From: Sean Christopherson <seanjc@google.com>
To: Maxim Levitsky <mlevitsk@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
x86@kernel.org, Borislav Petkov <bp@alien8.de>,
Paolo Bonzini <pbonzini@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH v2 0/3] Fix 'Spurious APIC interrupt (vector 0xFF) on CPU#n' issue
Date: Fri, 28 Jul 2023 18:41:12 -0700 [thread overview]
Message-ID: <ZMRuON4m1qZZWWip@google.com> (raw)
In-Reply-To: <20230726135945.260841-1-mlevitsk@redhat.com>
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.
next prev parent reply other threads:[~2023-07-29 1:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 13:59 [PATCH v2 0/3] Fix 'Spurious APIC interrupt (vector 0xFF) on CPU#n' issue Maxim Levitsky
2023-07-26 13:59 ` [PATCH v2 1/3] KVM: x86: VMX: __kvm_apic_update_irr must update the IRR atomically Maxim Levitsky
2023-07-26 13:59 ` [PATCH v2 2/3] KVM: x86: VMX: set irr_pending in kvm_apic_update_irr Maxim Levitsky
2023-07-26 13:59 ` [PATCH v2 3/3] KVM: x86: check the kvm_cpu_get_interrupt result before using it Maxim Levitsky
2023-07-29 1:41 ` Sean Christopherson [this message]
2023-07-29 14:27 ` [PATCH v2 0/3] Fix 'Spurious APIC interrupt (vector 0xFF) on CPU#n' issue Paolo Bonzini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZMRuON4m1qZZWWip@google.com \
--to=seanjc@google.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mlevitsk@redhat.com \
--cc=pbonzini@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox