From: Chao Gao <chao.gao@intel.com>
To: Sean Christopherson <seanjc@google.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, <kvm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, Zeng Guang <guang.zeng@intel.com>
Subject: Re: [PATCH 0/6] KVM: nVMX: Fix IPIv vs. nested posted interrupts
Date: Mon, 22 Jul 2024 20:55:07 +0800 [thread overview]
Message-ID: <Zp5Wq1h40JMSYL5a@chao-email> (raw)
In-Reply-To: <20240720000138.3027780-1-seanjc@google.com>
On Fri, Jul 19, 2024 at 05:01:32PM -0700, Sean Christopherson wrote:
>Fix a bug where KVM injects L2's nested posted interrupt into L1 as a
>nested VM-Exit instead of triggering PI processing. The actual bug is
>technically a generic nested posted interrupts problem, but due to the
>way that KVM handles interrupt delivery, I'm 99.9% certain the issue is
>limited to IPI virtualization being enabled.
Theoretically VT-d posted interrupt can also trigger this issue.
The fix looks good to me. For the whole series:
Reviewed-by: Chao Gao <chao.gao@intel.com>
next prev parent reply other threads:[~2024-07-22 12:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-20 0:01 [PATCH 0/6] KVM: nVMX: Fix IPIv vs. nested posted interrupts Sean Christopherson
2024-07-20 0:01 ` [PATCH 1/6] KVM: nVMX: Get to-be-acknowledge IRQ for nested VM-Exit at injection site Sean Christopherson
2024-09-04 21:08 ` Nathan Chancellor
2024-09-04 22:49 ` Sean Christopherson
2024-09-05 0:37 ` Sean Christopherson
2024-07-20 0:01 ` [PATCH 2/6] KVM: nVMX: Suppress external interrupt VM-Exit injection if there's no IRQ Sean Christopherson
2024-07-20 0:01 ` [PATCH 3/6] KVM: x86: Don't move VMX's nested PI notification vector from IRR to ISR Sean Christopherson
2024-07-20 0:01 ` [PATCH 4/6] KVM: nVMX: Track nested_vmx.posted_intr_nv as a signed int Sean Christopherson
2024-07-20 0:01 ` [PATCH 5/6] KVM: nVMX: Explicitly invalidate posted_intr_nv if PI is disabled at VM-Enter Sean Christopherson
2024-07-20 0:01 ` [PATCH 6/6] KVM: nVMX: Detect nested posted interrupt NV at nested VM-Exit injection Sean Christopherson
2024-07-23 14:49 ` Chao Gao
2024-07-23 17:43 ` Sean Christopherson
2024-07-22 12:55 ` Chao Gao [this message]
2024-07-22 23:58 ` [PATCH 0/6] KVM: nVMX: Fix IPIv vs. nested posted interrupts Sean Christopherson
2024-08-31 0:21 ` Sean Christopherson
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=Zp5Wq1h40JMSYL5a@chao-email \
--to=chao.gao@intel.com \
--cc=guang.zeng@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
/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