summaryrefslogtreecommitdiffstats
path: root/arch/powerpc/kvm/44x_tlb.c
diff options
context:
space:
mode:
authorJan Kiszka <jan.kiszka@siemens.com>2010-05-11 15:16:46 +0200
committerMarcelo Tosatti <mtosatti@redhat.com>2010-05-13 06:31:37 +0200
commitf8c5fae16649445e15656667f72bd51d777f7766 (patch)
treec4744f5024da012bbe9658dc4e80601fb3197281 /arch/powerpc/kvm/44x_tlb.c
parentKVM: x86: Call vcpu_load and vcpu_put in cpuid_update (diff)
downloadlinux-f8c5fae16649445e15656667f72bd51d777f7766.tar.xz
linux-f8c5fae16649445e15656667f72bd51d777f7766.zip
KVM: VMX: blocked-by-sti must not defer NMI injections
As the processor may not consider GUEST_INTR_STATE_STI as a reason for blocking NMI, it could return immediately with EXIT_REASON_NMI_WINDOW when we asked for it. But as we consider this state as NMI-blocking, we can run into an endless loop. Resolve this by allowing NMI injection if just GUEST_INTR_STATE_STI is active (originally suggested by Gleb). Intel confirmed that this is safe, the processor will never complain about NMI injection in this state. Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com> KVM-Stable-Tag Acked-by: Gleb Natapov <gleb@redhat.com> Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
Diffstat (limited to 'arch/powerpc/kvm/44x_tlb.c')
0 files changed, 0 insertions, 0 deletions