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
| File | Mode | Size |
|---|---|---|
| pci | ||
| Kconfig | -rw-r--r-- | 540 bytes |
| Makefile | -rw-r--r-- | 174 bytes |
| vfio.c | -rw-r--r-- | 36.5 KB |
| vfio_iommu_spapr_tce.c | -rw-r--r-- | 9.5 KB |
| vfio_iommu_type1.c | -rw-r--r-- | 21.9 KB |
Computing file changes ...
