From: Sean Christopherson <seanjc@google.com>
To: "Naveen N Rao (AMD)" <naveen@kernel.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org, Jim Mattson <jmattson@google.com>,
Maxim Levitsky <mlevitsk@redhat.com>,
Vasant Hegde <vasant.hegde@amd.com>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
Nikunj A Dadhania <nikunj@amd.com>,
Alejandro Jimenez <alejandro.j.jimenez@oracle.com>,
Joao Martins <joao.m.martins@oracle.com>,
"Maciej S. Szmigiero" <maciej.szmigiero@oracle.com>
Subject: Re: [RFC PATCH v2 2/5] KVM: SVM: Simplify the message printed with 'force_avic'
Date: Mon, 15 Sep 2025 15:42:32 -0700 [thread overview]
Message-ID: <aMiWWM6hb-Cm3QK3@google.com> (raw)
In-Reply-To: <5ebb7b1c278b6f20ee4f7afa0228298f9e504fbd.1756993734.git.naveen@kernel.org>
On Thu, Sep 04, 2025, Naveen N Rao (AMD) wrote:
> On systems that do not advertise support for AVIC, it can be
> force-enabled through 'force_avic' module parameter. In that case, a
> warning is displayed but the customary "AVIC enabled" message isn't.
> Fix that by printing "AVIC enabled" unconditionally. The warning for
> 'force_avic' is also needlessly long. Simplify the same.
>
> Signed-off-by: Naveen N Rao (AMD) <naveen@kernel.org>
> ---
> arch/x86/kvm/svm/avic.c | 12 ++----------
> 1 file changed, 2 insertions(+), 10 deletions(-)
>
> diff --git a/arch/x86/kvm/svm/avic.c b/arch/x86/kvm/svm/avic.c
> index 346cd23a43a9..3faed85fcacd 100644
> --- a/arch/x86/kvm/svm/avic.c
> +++ b/arch/x86/kvm/svm/avic.c
> @@ -1110,16 +1110,8 @@ bool avic_hardware_setup(void)
> return false;
> }
>
> - if (boot_cpu_has(X86_FEATURE_AVIC)) {
> - pr_info("AVIC enabled\n");
> - } else if (force_avic) {
> - /*
> - * Some older systems does not advertise AVIC support.
> - * See Revision Guide for specific AMD processor for more detail.
> - */
> - pr_warn("AVIC is not supported in CPUID but force enabled");
> - pr_warn("Your system might crash and burn");
> - }
> + pr_info("AVIC enabled%s\n", cpu_feature_enabled(X86_FEATURE_AVIC) ? "" :
> + " (forced, your system may crash and burn)");
Except this bundles the scary forced message into pr_info, which isn't desirable
since KVM really should "yell" about AVIC being force enabled. I 100% agree that
not printing "AVIC enabled" is mean, but I think we should do the super simple
thing and just always print exactly that.
>
> /* AVIC is a prerequisite for x2AVIC. */
> x2avic_enabled = boot_cpu_has(X86_FEATURE_X2AVIC);
> --
> 2.50.1
>
next prev parent reply other threads:[~2025-09-15 22:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-04 18:00 [RFC PATCH v2 0/5] KVM: SVM: Enable AVIC by default on Zen 4+ Naveen N Rao (AMD)
2025-09-04 18:00 ` [RFC PATCH v2 1/5] KVM: SVM: Stop warning if x2AVIC feature bit alone is enabled Naveen N Rao (AMD)
2025-09-15 20:04 ` Sean Christopherson
2025-09-16 7:14 ` Naveen N Rao
2025-09-16 13:40 ` Mario Limonciello
2025-09-16 13:51 ` Sean Christopherson
2025-09-16 18:37 ` Naveen N Rao
2025-09-16 19:26 ` Mario Limonciello
2025-09-17 0:44 ` Sean Christopherson
2025-09-04 18:00 ` [RFC PATCH v2 2/5] KVM: SVM: Simplify the message printed with 'force_avic' Naveen N Rao (AMD)
2025-09-15 22:42 ` Sean Christopherson [this message]
2025-09-04 18:00 ` [RFC PATCH v2 3/5] KVM: SVM: Move all AVIC setup to avic_hardware_setup() Naveen N Rao (AMD)
2025-09-15 19:59 ` Sean Christopherson
2025-09-04 18:00 ` [RFC PATCH v2 4/5] KVM: SVM: Move 'force_avic' module parameter to svm.c Naveen N Rao (AMD)
2025-09-15 22:43 ` Sean Christopherson
2025-09-04 18:00 ` [RFC PATCH v2 5/5] KVM: SVM: Enable AVIC by default from Zen 4 Naveen N Rao (AMD)
2025-09-15 22:53 ` Sean Christopherson
2025-09-16 7:39 ` Naveen N Rao
2025-09-16 14:27 ` Sean Christopherson
2025-09-16 18:53 ` Naveen N Rao
2025-09-15 23:17 ` Sean Christopherson
2025-09-16 10:17 ` Naveen N Rao
2025-09-15 23:23 ` [RFC PATCH v2 0/5] KVM: SVM: Enable AVIC by default on Zen 4+ Sean Christopherson
2025-09-16 10:31 ` 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=aMiWWM6hb-Cm3QK3@google.com \
--to=seanjc@google.com \
--cc=alejandro.j.jimenez@oracle.com \
--cc=jmattson@google.com \
--cc=joao.m.martins@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=maciej.szmigiero@oracle.com \
--cc=mlevitsk@redhat.com \
--cc=naveen@kernel.org \
--cc=nikunj@amd.com \
--cc=pbonzini@redhat.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=vasant.hegde@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