diff options
author | Paolo Bonzini <pbonzini@redhat.com> | 2020-11-05 17:20:49 +0100 |
---|---|---|
committer | Paolo Bonzini <pbonzini@redhat.com> | 2020-11-15 15:49:08 +0100 |
commit | 1c96dcceaeb3a99aaf0d548eef2223e0b02a7e40 (patch) | |
tree | ab8b7e8b8783bbdea64cc86b53ae50b893baa066 /drivers/i2c/busses/i2c-sis5595.c | |
parent | KVM: selftests: Verify supported CR4 bits can be set before KVM_SET_CPUID2 (diff) | |
download | linux-1c96dcceaeb3a99aaf0d548eef2223e0b02a7e40.tar.xz linux-1c96dcceaeb3a99aaf0d548eef2223e0b02a7e40.zip |
KVM: x86: fix apic_accept_events vs check_nested_events
vmx_apic_init_signal_blocked is buggy in that it returns true
even in VMX non-root mode. In non-root mode, however, INITs
are not latched, they just cause a vmexit. Previously,
KVM was waiting for them to be processed when kvm_apic_accept_events
and in the meanwhile it ate the SIPIs that the processor received.
However, in order to implement the wait-for-SIPI activity state,
KVM will have to process KVM_APIC_SIPI in vmx_check_nested_events,
and it will not be possible anymore to disregard SIPIs in non-root
mode as the code is currently doing.
By calling kvm_x86_ops.nested_ops->check_events, we can force a vmexit
(with the side-effect of latching INITs) before incorrectly injecting
an INIT or SIPI in a guest, and therefore vmx_apic_init_signal_blocked
can do the right thing.
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'drivers/i2c/busses/i2c-sis5595.c')
0 files changed, 0 insertions, 0 deletions