]> git.ipfire.org Git - thirdparty/kernel/stable.git/commitdiff
KVM: nVMX: Defer SVI update to vmcs01 on EOI when L2 is active w/o VID
authorChao Gao <chao.gao@intel.com>
Thu, 28 Nov 2024 00:00:10 +0000 (16:00 -0800)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Thu, 27 Feb 2025 12:30:14 +0000 (04:30 -0800)
[ Upstream commit 04bc93cf49d16d01753b95ddb5d4f230b809a991 ]

If KVM emulates an EOI for L1's virtual APIC while L2 is active, defer
updating GUEST_INTERUPT_STATUS.SVI, i.e. the VMCS's cache of the highest
in-service IRQ, until L1 is active, as vmcs01, not vmcs02, needs to track
vISR.  The missed SVI update for vmcs01 can result in L1 interrupts being
incorrectly blocked, e.g. if there is a pending interrupt with lower
priority than the interrupt that was EOI'd.

This bug only affects use cases where L1's vAPIC is effectively passed
through to L2, e.g. in a pKVM scenario where L2 is L1's depriveleged host,
as KVM will only emulate an EOI for L1's vAPIC if Virtual Interrupt
Delivery (VID) is disabled in vmc12, and L1 isn't intercepting L2 accesses
to its (virtual) APIC page (or if x2APIC is enabled, the EOI MSR).

WARN() if KVM updates L1's ISR while L2 is active with VID enabled, as an
EOI from L2 is supposed to affect L2's vAPIC, but still defer the update,
to try to keep L1 alive.  Specifically, KVM forwards all APICv-related
VM-Exits to L1 via nested_vmx_l1_wants_exit():

case EXIT_REASON_APIC_ACCESS:
case EXIT_REASON_APIC_WRITE:
case EXIT_REASON_EOI_INDUCED:
/*
 * The controls for "virtualize APIC accesses," "APIC-
 * register virtualization," and "virtual-interrupt
 * delivery" only come from vmcs12.
 */
return true;

Fixes: c7c9c56ca26f ("x86, apicv: add virtual interrupt delivery support")
Cc: stable@vger.kernel.org
Link: https://lore.kernel.org/kvm/20230312180048.1778187-1-jason.cj.chen@intel.com
Reported-by: Markku Ahvenjärvi <mankku@gmail.com>
Closes: https://lore.kernel.org/all/20240920080012.74405-1-mankku@gmail.com
Cc: Janne Karhunen <janne.karhunen@gmail.com>
Signed-off-by: Chao Gao <chao.gao@intel.com>
[sean: drop request, handle in VMX, write changelog]
Tested-by: Chao Gao <chao.gao@intel.com>
Link: https://lore.kernel.org/r/20241128000010.4051275-3-seanjc@google.com
Signed-off-by: Sean Christopherson <seanjc@google.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
arch/x86/kvm/lapic.c
arch/x86/kvm/lapic.h
arch/x86/kvm/vmx/nested.c
arch/x86/kvm/vmx/vmx.c
arch/x86/kvm/vmx/vmx.h

index 375bbb9600d3c10689fc0a8d3ebab57fa48e1059..1a8148dec4afe9fbeb07f3aa7ea034c3dcee821d 100644 (file)
@@ -816,6 +816,17 @@ static inline void apic_clear_isr(int vec, struct kvm_lapic *apic)
        }
 }
 
+void kvm_apic_update_hwapic_isr(struct kvm_vcpu *vcpu)
+{
+       struct kvm_lapic *apic = vcpu->arch.apic;
+
+       if (WARN_ON_ONCE(!lapic_in_kernel(vcpu)) || !apic->apicv_active)
+               return;
+
+       kvm_x86_call(hwapic_isr_update)(vcpu, apic_find_highest_isr(apic));
+}
+EXPORT_SYMBOL_GPL(kvm_apic_update_hwapic_isr);
+
 int kvm_lapic_find_highest_irr(struct kvm_vcpu *vcpu)
 {
        /* This may race with setting of irr in __apic_accept_irq() and
index fc4bd36d44cfc2f3d231df4e27af4dc6c8746ab4..3aa599db779689f3015f4f945fb9db2d0dd1df86 100644 (file)
@@ -120,6 +120,7 @@ void kvm_apic_send_ipi(struct kvm_lapic *apic, u32 icr_low, u32 icr_high);
 int kvm_set_apic_base(struct kvm_vcpu *vcpu, struct msr_data *msr_info);
 int kvm_apic_get_state(struct kvm_vcpu *vcpu, struct kvm_lapic_state *s);
 int kvm_apic_set_state(struct kvm_vcpu *vcpu, struct kvm_lapic_state *s);
+void kvm_apic_update_hwapic_isr(struct kvm_vcpu *vcpu);
 int kvm_lapic_find_highest_irr(struct kvm_vcpu *vcpu);
 
 u64 kvm_get_lapic_tscdeadline_msr(struct kvm_vcpu *vcpu);
index 931a7361c30f2da28073eb832efce0b378e3b325..22bee8a711442de6191887d91a0521015c31d7e9 100644 (file)
@@ -5043,6 +5043,11 @@ void nested_vmx_vmexit(struct kvm_vcpu *vcpu, u32 vm_exit_reason,
                kvm_make_request(KVM_REQ_APICV_UPDATE, vcpu);
        }
 
+       if (vmx->nested.update_vmcs01_hwapic_isr) {
+               vmx->nested.update_vmcs01_hwapic_isr = false;
+               kvm_apic_update_hwapic_isr(vcpu);
+       }
+
        if ((vm_exit_reason != -1) &&
            (enable_shadow_vmcs || nested_vmx_is_evmptr12_valid(vmx)))
                vmx->nested.need_vmcs12_to_shadow_sync = true;
index f06d443ec3c68dbe8474590fc5093f59b865f3dc..1af30e3472cdd97ed1fef070e53d0e77ebe3e6bb 100644 (file)
@@ -6858,6 +6858,27 @@ void vmx_hwapic_isr_update(struct kvm_vcpu *vcpu, int max_isr)
        u16 status;
        u8 old;
 
+       /*
+        * If L2 is active, defer the SVI update until vmcs01 is loaded, as SVI
+        * is only relevant for if and only if Virtual Interrupt Delivery is
+        * enabled in vmcs12, and if VID is enabled then L2 EOIs affect L2's
+        * vAPIC, not L1's vAPIC.  KVM must update vmcs01 on the next nested
+        * VM-Exit, otherwise L1 with run with a stale SVI.
+        */
+       if (is_guest_mode(vcpu)) {
+               /*
+                * KVM is supposed to forward intercepted L2 EOIs to L1 if VID
+                * is enabled in vmcs12; as above, the EOIs affect L2's vAPIC.
+                * Note, userspace can stuff state while L2 is active; assert
+                * that VID is disabled if and only if the vCPU is in KVM_RUN
+                * to avoid false positives if userspace is setting APIC state.
+                */
+               WARN_ON_ONCE(vcpu->wants_to_run &&
+                            nested_cpu_has_vid(get_vmcs12(vcpu)));
+               to_vmx(vcpu)->nested.update_vmcs01_hwapic_isr = true;
+               return;
+       }
+
        if (max_isr == -1)
                max_isr = 0;
 
index 2325f773a20be0ea8068675a17c634c15984f41d..41bf59bbc6426c71977179b547fa4d85af95ff4b 100644 (file)
@@ -176,6 +176,7 @@ struct nested_vmx {
        bool reload_vmcs01_apic_access_page;
        bool update_vmcs01_cpu_dirty_logging;
        bool update_vmcs01_apicv_status;
+       bool update_vmcs01_hwapic_isr;
 
        /*
         * Enlightened VMCS has been enabled. It does not mean that L1 has to