Revision 596f3142d2b7be307a1652d59e7b93adab918437 authored by Radim Krčmář on 11 March 2014, 18:11:18 UTC, committed by Paolo Bonzini on 12 March 2014, 17:21:10 UTC
We always disable cr8 intercept in its handler, but only re-enable it
if handling KVM_REQ_EVENT, so there can be a window where we do not
intercept cr8 writes, which allows an interrupt to disrupt a higher
priority task.

Fix this by disabling intercepts in the same function that re-enables
them when needed. This fixes BSOD in Windows 2008.

Cc: <stable@vger.kernel.org>
Signed-off-by: Radim Krčmář <rkrcmar@redhat.com>
Reviewed-by: Marcelo Tosatti <mtosatti@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
1 parent 6cbde82
History
File Mode Size
Kconfig -rw-r--r-- 2.2 KB
Makefile -rw-r--r-- 484 bytes
extcon-adc-jack.c -rw-r--r-- 4.9 KB
extcon-arizona.c -rw-r--r-- 37.3 KB
extcon-class.c -rw-r--r-- 22.6 KB
extcon-gpio.c -rw-r--r-- 5.0 KB
extcon-max14577.c -rw-r--r-- 20.2 KB
extcon-max77693.c -rw-r--r-- 37.6 KB
extcon-max8997.c -rw-r--r-- 21.0 KB
extcon-palmas.c -rw-r--r-- 9.1 KB
of_extcon.c -rw-r--r-- 1.8 KB

back to top