From: Sean Christopherson <seanjc@google.com>
To: Naveen N Rao <naveen@kernel.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org, Dmytro Maluka <dmaluka@chromium.org>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
Subject: Re: [PATCH] KVM: SVM: Clear AVIC Physical ID table entry if vCPU creation fails
Date: Tue, 22 Sep 2026 16:07:39 -0700 [thread overview]
Message-ID: <arMKOysEYFt_t4go@google.com> (raw)
In-Reply-To: <arLm-7h6nllfVpdT@blrnaveerao1>
On Wed, Sep 23, 2026, Naveen N Rao wrote:
> On Tue, Sep 22, 2026 at 12:36:15PM -0700, Sean Christopherson wrote:
> Yes, this LGTM, with a minor fix below.
>
> >
> > diff --git arch/x86/kvm/svm/avic.c arch/x86/kvm/svm/avic.c
> > index 3b037e385523..e767e43bfb40 100644
> > --- arch/x86/kvm/svm/avic.c
> > +++ arch/x86/kvm/svm/avic.c
> > @@ -395,6 +395,11 @@ static phys_addr_t avic_get_backing_page_address(struct vcpu_svm *svm)
> > return __sme_set(__pa(svm->vcpu.arch.apic->regs));
> > }
> >
> > +static bool avic_is_addressable_vcpu(struct kvm_vcpu *vcpu)
> > +{
> > + return vcpu->vcpu_id <= __avic_get_max_physical_id(vcpu->kvm, NULL);
> > +}
> > +
> > void avic_init_vmcb(struct vcpu_svm *svm, struct vmcb *vmcb)
> > {
> > struct kvm_svm *kvm_svm = to_kvm_svm(svm->vcpu.kvm);
> > @@ -412,7 +417,6 @@ void avic_init_vmcb(struct vcpu_svm *svm, struct vmcb *vmcb)
> >
> > static int avic_init_backing_page(struct kvm_vcpu *vcpu)
> > {
> > - u32 max_id = x2avic_enabled ? x2avic_max_physical_id : AVIC_MAX_PHYSICAL_ID;
> > struct kvm_svm *kvm_svm = to_kvm_svm(vcpu->kvm);
> > struct vcpu_svm *svm = to_svm(vcpu);
> > u32 id = vcpu->vcpu_id;
> > @@ -425,7 +429,7 @@ static int avic_init_backing_page(struct kvm_vcpu *vcpu)
> > * avic_vcpu_load() expects to be called if and only if the vCPU has
> > * fully initialized AVIC.
> > */
> > - if (id > max_id) {
> > + if (avic_is_addressable_vcpu(vcpu)) {
>
> Missing a negation there:
> if (!avic_is_addressable_vcpu(vcpu))
Heh, I discovered this literally ~10 seconds before reading your mail. Hooray
for tests!
> ... which also means all three places are inverting the check, so you
> could optionally flip the helper instead.
I'll keep it as is, Paolo generally prefers "positive" predicates, and I tend to
agree with him, e.g. it makes it the error paths more obvious (the above bug
notwithstanding).
next prev parent reply other threads:[~2026-09-22 23:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 6:28 [PATCH] KVM: SVM: Clear AVIC Physical ID table entry if vCPU creation fails Naveen N Rao (AMD)
2026-09-09 3:09 ` Atish Patra
2026-09-11 18:55 ` Sean Christopherson
2026-09-22 18:19 ` Naveen N Rao
2026-09-22 19:08 ` Sean Christopherson
2026-09-22 19:36 ` Sean Christopherson
2026-09-22 20:43 ` Naveen N Rao
2026-09-22 23:07 ` Sean Christopherson [this message]
2026-09-22 19:37 ` Naveen N Rao
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=arMKOysEYFt_t4go@google.com \
--to=seanjc@google.com \
--cc=dmaluka@chromium.org \
--cc=kvm@vger.kernel.org \
--cc=naveen@kernel.org \
--cc=pbonzini@redhat.com \
--cc=suravee.suthikulpanit@amd.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