From: Sean Christopherson <seanjc@google.com>
To: Naveen N Rao <naveen@kernel.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 6/6] KVM: SVM: Enable AVIC by default for Zen4+ if x2AVIC is support
Date: Fri, 19 Sep 2025 14:56:49 -0700 [thread overview]
Message-ID: <aM3RoW3MzUfp-yto@google.com> (raw)
In-Reply-To: <4vqqbmsqcaeabbslmrmxbtrq4wubt2avhimijk3xqgerkifune@ahyotfj55gds>
On Fri, Sep 19, 2025, Naveen N Rao wrote:
> On Thu, Sep 18, 2025 at 05:21:36PM -0700, Sean Christopherson wrote:
> > @@ -1151,6 +1170,18 @@ void avic_vcpu_unblocking(struct kvm_vcpu *vcpu)
> >
> > static bool __init avic_want_avic_enable(void)
> > {
> > + /*
> > + * In "auto" mode, enable AVIC by default for Zen4+ if x2AVIC is
> > + * supported (to avoid enabling partial support by default, and because
> > + * x2AVIC should be supported by all Zen4+ CPUs). Explicitly check for
> > + * family 0x19 and later (Zen5+), as the kernel's synthetic ZenX flags
> > + * aren't inclusive of previous generations, i.e. the kernel will set
> > + * at most one ZenX feature flag.
> > + */
> > + if (avic == AVIC_AUTO_MODE)
> > + avic = boot_cpu_has(X86_FEATURE_X2AVIC) &&
>
> This can use cpu_feature_enabled() as well, I think.
It could, but I'm going to leave it as boot_cpu_has() for now, purely because
the existing code uses boot_cpu_has() for X2AVIC and mixing the two adds
"complexity" where none exists.
I'm definitely not opposed to using cpu_feature_enabled() in general, just not
in this case (of course, we could just swap them all, but meh, it's init code).
next prev parent reply other threads:[~2025-09-19 21:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-19 0:21 [PATCH v3 0/6] KVM: SVM: Enable AVIC for Zen4+ (if x2AVIC) Sean Christopherson
2025-09-19 0:21 ` [PATCH v3 1/6] KVM: SVM: Move x2AVIC MSR interception helper to avic.c Sean Christopherson
2025-09-19 9:35 ` Naveen N Rao
2025-09-19 0:21 ` [PATCH v3 2/6] KVM: SVM: Update "APICv in x2APIC without x2AVIC" in avic.c, not svm.c Sean Christopherson
2025-09-19 9:42 ` Naveen N Rao
2025-09-19 14:21 ` Sean Christopherson
2025-09-22 7:08 ` Chao Gao
2025-09-19 0:21 ` [PATCH v3 3/6] KVM: SVM: Always print "AVIC enabled" separately, even when force enabled Sean Christopherson
2025-09-19 9:52 ` Naveen N Rao
2025-09-19 0:21 ` [PATCH v3 4/6] KVM: SVM: Don't advise the user to do force_avic=y (when x2AVIC is detected) Sean Christopherson
2025-09-19 10:26 ` Naveen N Rao
2025-09-19 0:21 ` [PATCH v3 5/6] KVM: SVM: Move global "avic" variable to avic.c Sean Christopherson
2025-09-19 10:31 ` Naveen N Rao
2025-09-19 14:44 ` Sean Christopherson
2025-09-19 18:27 ` Naveen N Rao
2025-09-19 0:21 ` [PATCH v3 6/6] KVM: SVM: Enable AVIC by default for Zen4+ if x2AVIC is support Sean Christopherson
2025-09-19 10:37 ` Naveen N Rao
2025-09-19 21:56 ` Sean Christopherson [this message]
2025-09-19 10:42 ` [PATCH v3 0/6] KVM: SVM: Enable AVIC for Zen4+ (if x2AVIC) 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=aM3RoW3MzUfp-yto@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=naveen@kernel.org \
--cc=pbonzini@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.