diff options
| author | Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com> | 2013-10-09 14:33:21 +0530 |
|---|---|---|
| committer | Gleb Natapov <gleb@redhat.com> | 2013-10-15 14:15:54 +0300 |
| commit | 3dbef3e3bf13d74582fe43548f5c570a0cec9b20 (patch) | |
| tree | d5aebb38746adcf68ce226d5b0f9f3093fc8b9e7 /arch/cris/mm/ioremap.c | |
| parent | 9d05746e7b16d8565dddbe3200faa1e669d23bbf (diff) | |
| download | linux-stable-3dbef3e3bf13d74582fe43548f5c570a0cec9b20.tar.gz linux-stable-3dbef3e3bf13d74582fe43548f5c570a0cec9b20.tar.bz2 linux-stable-3dbef3e3bf13d74582fe43548f5c570a0cec9b20.zip | |
KVM: Enable pvspinlock after jump_label_init() to avoid VM hang
We use jump label to enable pv-spinlock. With the changes in (442e0973e927
Merge branch 'x86/jumplabel'), the jump label behaviour has changed
that would result in eventual hang of the VM since we would end up in a
situation where slow path locks would halt the vcpus but we will not be
able to wakeup the vcpu by lock releaser using unlock kick.
Similar problem in Xen and more detailed description is available in
a945928ea270 (xen: Do not enable spinlocks before jump_label_init()
has executed)
This patch splits kvm_spinlock_init to separate jump label changes with
pvops patching and also make jump label enabling after jump_label_init().
Signed-off-by: Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
Reviewed-by: Steven Rostedt <rostedt@goodmis.org>
Signed-off-by: Gleb Natapov <gleb@redhat.com>
Diffstat (limited to 'arch/cris/mm/ioremap.c')
0 files changed, 0 insertions, 0 deletions