[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZMRuON4m1qZZWWip@google.com>
Date: Fri, 28 Jul 2023 18:41:12 -0700
From: Sean Christopherson <seanjc@...gle.com>
To: Maxim Levitsky <mlevitsk@...hat.com>
Cc: kvm@...r.kernel.org, linux-kernel@...r.kernel.org, x86@...nel.org,
Borislav Petkov <bp@...en8.de>,
Paolo Bonzini <pbonzini@...hat.com>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Thomas Gleixner <tglx@...utronix.de>,
"H. Peter Anvin" <hpa@...or.com>, Ingo Molnar <mingo@...hat.com>
Subject: Re: [PATCH v2 0/3] Fix 'Spurious APIC interrupt (vector 0xFF) on
CPU#n' issue
On Wed, Jul 26, 2023, Maxim Levitsky wrote:
> Maxim Levitsky (3):
> KVM: x86: VMX: __kvm_apic_update_irr must update the IRR atomically
> KVM: x86: VMX: set irr_pending in kvm_apic_update_irr
> KVM: x86: check the kvm_cpu_get_interrupt result before using it
>
> arch/x86/kvm/lapic.c | 25 +++++++++++++++++--------
> arch/x86/kvm/x86.c | 10 +++++++---
> 2 files changed, 24 insertions(+), 11 deletions(-)
Paolo, are you still planning on taking these directly? I can also grab them
and send them your way next week. I have a couple of (not super urgent, but
kinda urgent) fixes for 6.5 that I'm planning on sending a PULL request for, just
didn't get around to that today.
Powered by blists - more mailing lists