xen/spinlock: Don't enable them unconditionally.
authorKonrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Fri, 4 Apr 2014 18:48:04 +0000 (14:48 -0400)
committerDavid Vrabel <david.vrabel@citrix.com>
Tue, 15 Apr 2014 16:41:28 +0000 (17:41 +0100)
commite0fc17a936334c08b2729fff87168c03fdecf5b6
tree8a42f8c774ddd37f5b74650b114a0cade7fd1cd9
parentc0914e61660fa7d501ef9394b26f4847ef3dc98e
xen/spinlock: Don't enable them unconditionally.

The git commit a945928ea2709bc0e8e8165d33aed855a0110279
('xen: Do not enable spinlocks before jump_label_init() has executed')
was added to deal with the jump machinery. Earlier the code
that turned on the jump label was only called by Xen specific
functions. But now that it had been moved to the initcall machinery
it gets called on Xen, KVM, and baremetal - ouch!. And the detection
machinery to only call it on Xen wasn't remembered in the heat
of merge window excitement.

This means that the slowpath is enabled on baremetal while it should
not be.

Reported-by: Waiman Long <waiman.long@hp.com>
Acked-by: Steven Rostedt <rostedt@goodmis.org>
CC: stable@vger.kernel.org
CC: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Signed-off-by: David Vrabel <david.vrabel@citrix.com>
arch/x86/xen/spinlock.c