diff options
author | Paolo Bonzini <pbonzini@redhat.com> | 2014-05-14 17:40:58 +0200 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2014-06-26 15:12:39 -0400 |
commit | 78d2f0ceb0665162059a6f40d1aa8e8ed999936d (patch) | |
tree | b27985dcb2e355b7cc34c34adb85d9c56bd51390 /arch/Kconfig | |
parent | 65df70793e5cce0b72f38172afa9ad32de92bf65 (diff) | |
download | linux-3.10-78d2f0ceb0665162059a6f40d1aa8e8ed999936d.tar.gz linux-3.10-78d2f0ceb0665162059a6f40d1aa8e8ed999936d.tar.bz2 linux-3.10-78d2f0ceb0665162059a6f40d1aa8e8ed999936d.zip |
KVM: lapic: sync highest ISR to hardware apic on EOI
commit fc57ac2c9ca8109ea97fcc594f4be436944230cc upstream.
When Hyper-V enlightenments are in effect, Windows prefers to issue an
Hyper-V MSR write to issue an EOI rather than an x2apic MSR write.
The Hyper-V MSR write is not handled by the processor, and besides
being slower, this also causes bugs with APIC virtualization. The
reason is that on EOI the processor will modify the highest in-service
interrupt (SVI) field of the VMCS, as explained in section 29.1.4 of
the SDM; every other step in EOI virtualization is already done by
apic_send_eoi or on VM entry, but this one is missing.
We need to do the same, and be careful not to muck with the isr_count
and highest_isr_cache fields that are unused when virtual interrupt
delivery is enabled.
Reviewed-by: Yang Zhang <yang.z.zhang@intel.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'arch/Kconfig')
0 files changed, 0 insertions, 0 deletions