From: Tao Su <tao1.su@linux.intel.com>
To: Chao Gao <chao.gao@intel.com>
Cc: kvm@vger.kernel.org, seanjc@google.com, pbonzini@redhat.com,
guang.zeng@intel.com, yi1.lai@intel.com
Subject: Re: [PATCH 2/2] KVM: x86: Clear X2APIC_ICR_UNUSED_12 after APIC-write VM-exit
Date: Mon, 4 Sep 2023 11:00:01 +0800 [thread overview]
Message-ID: <ZPVIMSfaWo9zRtIq@linux.bj.intel.com> (raw)
In-Reply-To: <ZPVFDiB+HojAxuIz@chao-email>
On Mon, Sep 04, 2023 at 10:46:38AM +0800, Chao Gao wrote:
> On Mon, Sep 04, 2023 at 09:35:55AM +0800, Tao Su wrote:
> >When IPI virtualization is enabled, a WARN is triggered if bit12 of ICR
> >MSR is set after APIC-write VM-exit. The reason is kvm_apic_send_ipi()
> >thinks the APIC_ICR_BUSY bit should be cleared because KVM has no delay,
> >but kvm_apic_write_nodecode() doesn't clear the APIC_ICR_BUSY bit.
> >
> >Since bit12 of ICR is no longer BUSY bit but UNUSED bit in x2APIC mode,
> >and SDM has no detail about how hardware will handle the UNUSED bit12
> >set, we tested on Intel CPU (SRF/GNR) with IPI virtualization and found
> >the UNUSED bit12 was also cleared by hardware without #GP. Therefore,
> >the clearing of bit12 should be still kept being consistent with the
> >hardware behavior.
> >
> >Fixes: 5413bcba7ed5 ("KVM: x86: Add support for vICR APIC-write VM-Exits in x2APIC mode")
> >Signed-off-by: Tao Su <tao1.su@linux.intel.com>
> >Tested-by: Yi Lai <yi1.lai@intel.com>
> >---
> > arch/x86/kvm/lapic.c | 27 ++++++++++++++++++++-------
> > 1 file changed, 20 insertions(+), 7 deletions(-)
> >
> >diff --git a/arch/x86/kvm/lapic.c b/arch/x86/kvm/lapic.c
> >index a983a16163b1..09a376aeb4a0 100644
> >--- a/arch/x86/kvm/lapic.c
> >+++ b/arch/x86/kvm/lapic.c
> >@@ -1482,8 +1482,17 @@ void kvm_apic_send_ipi(struct kvm_lapic *apic, u32 icr_low, u32 icr_high)
> > {
> > struct kvm_lapic_irq irq;
> >
> >- /* KVM has no delay and should always clear the BUSY/PENDING flag. */
> >- WARN_ON_ONCE(icr_low & APIC_ICR_BUSY);
> >+ /*
> >+ * In non-x2apic mode, KVM has no delay and should always clear the
> >+ * BUSY/PENDING flag. In x2apic mode, KVM should clear the unused bit12
> >+ * of ICR since hardware will also clear this bit. Although
> >+ * APIC_ICR_BUSY and X2APIC_ICR_UNUSED_12 are same, they mean different
> >+ * things in different modes.
> >+ */
> >+ if (!apic_x2apic_mode(apic))
> >+ WARN_ON_ONCE(icr_low & APIC_ICR_BUSY);
> >+ else
> >+ WARN_ON_ONCE(icr_low & X2APIC_ICR_UNUSED_12);
>
>
> Hi Tao,
>
> Using the alias for APIC_ICR_BUSY is not strictly necessary for the bug fix.
> I think it is better to move this hunk into patch 1.
>
> >
> > irq.vector = icr_low & APIC_VECTOR_MASK;
> > irq.delivery_mode = icr_low & APIC_MODE_MASK;
> >@@ -2429,13 +2438,12 @@ void kvm_apic_write_nodecode(struct kvm_vcpu *vcpu, u32 offset)
> > * ICR is a single 64-bit register when x2APIC is enabled. For legacy
> > * xAPIC, ICR writes need to go down the common (slightly slower) path
> > * to get the upper half from ICR2.
> >+ *
> >+ * TODO: optimize to just emulate side effect w/o one more write
> > */
> > if (apic_x2apic_mode(apic) && offset == APIC_ICR) {
> >- val = kvm_lapic_get_reg64(apic, APIC_ICR);
> >- kvm_apic_send_ipi(apic, (u32)val, (u32)(val >> 32));
> >- trace_kvm_apic_write(APIC_ICR, val);
> >+ kvm_x2apic_icr_write(apic, val);
> > } else {
> >- /* TODO: optimize to just emulate side effect w/o one more write */
> > val = kvm_lapic_get_reg(apic, offset);
> > kvm_lapic_reg_write(apic, offset, (u32)val);
> > }
> >@@ -3122,7 +3130,12 @@ int kvm_lapic_set_vapic_addr(struct kvm_vcpu *vcpu, gpa_t vapic_addr)
> >
> > int kvm_x2apic_icr_write(struct kvm_lapic *apic, u64 data)
> > {
> >- data &= ~APIC_ICR_BUSY;
> >+ /*
> >+ * The Delivery Status Bit(bit 12) is removed in x2apic mode, but this
> >+ * bit is also cleared by hardware, so keep consistent with hardware
> >+ * behavior to clear this bit.
> >+ */
> >+ data &= ~X2APIC_ICR_UNUSED_12;
>
> Ditto.
>
> and can you also swap patch 1 with patch 2? Because patch 1 is an optional
> improvement, putting such a patch at the end of a patch set gives
> maintainers an easy choice about whether they want it or not.
Yes, I just think the alias will make the code clearer because x2APIC
does remove bit12. If it is not necessary, I will directly drop this
alias in version 2.
Thanks,
Tao
>
> >
> > kvm_apic_send_ipi(apic, (u32)data, (u32)(data >> 32));
> > kvm_lapic_set_reg64(apic, APIC_ICR, data);
> >--
> >2.34.1
> >
next prev parent reply other threads:[~2023-09-04 3:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 1:35 [PATCH 0/2] KVM: x86: Fix a WARN in kvm_apic_send_ipi() Tao Su
2023-09-04 1:35 ` [PATCH 1/2] x86/apic: Introduce X2APIC_ICR_UNUSED_12 for x2APIC mode Tao Su
2023-09-04 2:58 ` Chao Gao
2023-09-04 3:03 ` Tao Su
2023-09-04 1:35 ` [PATCH 2/2] KVM: x86: Clear X2APIC_ICR_UNUSED_12 after APIC-write VM-exit Tao Su
2023-09-04 2:46 ` Chao Gao
2023-09-04 3:00 ` Tao Su [this message]
2023-09-04 4:16 ` kernel test robot
2023-09-04 5:02 ` Tao Su
2023-09-05 23:03 ` Sean Christopherson
2023-09-06 5:07 ` Tao Su
2023-09-06 22:17 ` Sean Christopherson
2023-09-07 9:56 ` Tao Su
2023-09-24 13:58 ` kernel test robot
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=ZPVIMSfaWo9zRtIq@linux.bj.intel.com \
--to=tao1.su@linux.intel.com \
--cc=chao.gao@intel.com \
--cc=guang.zeng@intel.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=yi1.lai@intel.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