From: Naveen N Rao <naveen@kernel.org>
To: Sean Christopherson <seanjc@google.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Alejandro Jimenez <alejandro.j.jimenez@oracle.com>
Subject: Re: [PATCH 1/3] KVM: SVM: Disable x2AVIC RDMSR interception for MSRs KVM actually supports
Date: Fri, 10 Apr 2026 22:15:39 +0530 [thread overview]
Message-ID: <adkl4wFdk4JrM3T-@blrnaveerao1> (raw)
In-Reply-To: <20260409222449.2013847-2-seanjc@google.com>
On Thu, Apr 09, 2026 at 03:24:47PM -0700, Sean Christopherson wrote:
> Fix multiple (classes of) bugs with one stone by using KVM's mask of
> readable local APIC registers to determine which x2APIC MSRs to pass
> through (or not) when toggling x2AVIC on/off. The existing hand-coded
> list of MSRs is wrong on multiple fronts:
>
> - ARBPRI, DFR, and ICR2 aren't supported by x2APIC; disabling
> interception is nonsensical and suboptimal (the access generates a
> #VMEXIT that requires decoding the instruction).
>
> - RRR is completely unsupported.
>
> - AVIC currently fails to pass through the "range of vectors" registers,
> IRR, ISR, and TMR, as e.g. X2APIC_MSR(APIC_IRR) only affects IRR0, and
> thus only disables intercept for vectors 31:0 (which are the *least*
> interesting registers).
:facepalm:
We seriously need better selftests for these. Also on my list has been
to cook up something for your other fix where AVIC gets inhibited for
non-zero vCPU IDs (with x2AVIC disabled):
http://lore.kernel.org/r/20260112232805.1512361-1-seanjc@google.com
I started looking at Alejandro's series adding AVIC-related binary
stats, but had to switch to other things. Last I looked, I felt that
your suggestion to add an "exits" array accounting individual #VMEXITs
would in particular be helpful:
https://lore.kernel.org/kvm/ZmMjHwavCLk0lRd7@google.com/
Though I'm not sure how standardizing this across VMX and SVM looks
like, and/or if it will be truly helpful -- we may be interested in
specific exits, such as AVIC-related exits for some of the tests...
Thoughts?
>
> Fixes: 4d1d7942e36a ("KVM: SVM: Introduce logic to (de)activate x2AVIC mode")
> Cc: stable@vger.kernel.org
> Cc: Naveen N Rao (AMD) <naveen@kernel.org>
> Signed-off-by: Sean Christopherson <seanjc@google.com>
> ---
> arch/x86/kvm/svm/avic.c | 13 +++++++++++--
> 1 file changed, 11 insertions(+), 2 deletions(-)
>
> diff --git a/arch/x86/kvm/svm/avic.c b/arch/x86/kvm/svm/avic.c
> index adf211860949..df974ee290d0 100644
> --- a/arch/x86/kvm/svm/avic.c
> +++ b/arch/x86/kvm/svm/avic.c
> @@ -122,6 +122,9 @@ static u32 x2avic_max_physical_id;
> static void avic_set_x2apic_msr_interception(struct vcpu_svm *svm,
> bool intercept)
> {
> + struct kvm_vcpu *vcpu = &svm->vcpu;
> + u64 x2apic_readable_mask;
> +
> static const u32 x2avic_passthrough_msrs[] = {
> X2APIC_MSR(APIC_ID),
> X2APIC_MSR(APIC_LVR),
> @@ -162,9 +165,15 @@ static void avic_set_x2apic_msr_interception(struct vcpu_svm *svm,
> if (!x2avic_enabled)
> return;
>
> + x2apic_readable_mask = kvm_lapic_readable_reg_mask(vcpu->arch.apic);
> +
> + for (i = 0; i < BITS_PER_TYPE(typeof(x2apic_readable_mask)); i++)
> + svm_set_intercept_for_msr(vcpu, APIC_BASE_MSR + i,
> + MSR_TYPE_R, intercept);
> +
Yet to test this series (will get to it next week in more detail), but I
suppose you meant to use `for_each_set_bit()` or such?
- Naveen
next prev parent reply other threads:[~2026-04-10 16:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 22:24 [PATCH 0/3] KVM: SVM: Fix x2AVIC MSR interception mess Sean Christopherson
2026-04-09 22:24 ` [PATCH 1/3] KVM: SVM: Disable x2AVIC RDMSR interception for MSRs KVM actually supports Sean Christopherson
2026-04-10 16:45 ` Naveen N Rao [this message]
2026-04-10 19:20 ` Sean Christopherson
2026-04-09 22:24 ` [PATCH 2/3] KVM: SVM: Always intercept RDMSR for TMCCT (current APIC timer count) Sean Christopherson
2026-04-09 22:24 ` [PATCH 3/3] KVM: SVM: Only disable x2AVIC WRMSR interception for MSRs that are accelerated Sean Christopherson
2026-04-10 16:53 ` Naveen N Rao
2026-04-10 17:19 ` 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=adkl4wFdk4JrM3T-@blrnaveerao1 \
--to=naveen@kernel.org \
--cc=alejandro.j.jimenez@oracle.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