From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Sean Christopherson <seanjc@google.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Paul Menzel <pmenzel@molgen.mpg.de>,
"Maciej S . Szmigiero" <mail@maciej.szmigiero.name>
Subject: Re: [PATCH 1/2] KVM: x86: Add vendor name to kvm_x86_ops, use it for error messages
Date: Fri, 22 Oct 2021 08:33:44 +0200 [thread overview]
Message-ID: <871r4dwotz.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <YXGn70lhcjulaO3r@google.com>
Sean Christopherson <seanjc@google.com> writes:
> On Thu, Oct 21, 2021, Vitaly Kuznetsov wrote:
>> > if (ops->disabled_by_bios()) {
>> > - pr_err_ratelimited("kvm: disabled by bios\n");
>> > + pr_err_ratelimited("kvm: support for '%s' disabled by bios\n",
>> > + ops->runtime_ops->name);
>>
>>
>> I'd suggest we change this to
>>
>> pr_err_ratelimited("kvm: %s: virtualization disabled in BIOS\n",
>> ops->runtime_ops->name);
>>
>> or something like that as generally, it makes little sense to search for
>> 'KVM' in BIOS settings. You need too look for either 'Virtualization' or
>> VT-x/AMD-v.
>
> I'd prefer to avoid VT-x/AMD-v so as not to speculate on the module being loaded
> or the underlying hardware, e.g. I've no idea what Hygon, Zhaoxin, etc... use for
> "code" names.
>
> What about
>
> pr_err_ratelimited("kvm: virtualization support for '%s' disabled by BIOS\n",
> ops->runtime_ops->name);
>
> to add the virtualization flavor but still make it clear that error is coming
> from the base kvm module.
Works for me, thanks! I just want to make sure people know what to do
when they see the message.
--
Vitaly
next prev parent reply other threads:[~2021-10-22 6:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-18 18:39 [PATCH 0/2] KVM: x86: Enhance vendor module error messages Sean Christopherson
2021-10-18 18:39 ` [PATCH 1/2] KVM: x86: Add vendor name to kvm_x86_ops, use it for " Sean Christopherson
2021-10-21 8:08 ` Vitaly Kuznetsov
2021-10-21 17:48 ` Sean Christopherson
2021-10-22 6:33 ` Vitaly Kuznetsov [this message]
2021-10-18 18:39 ` [PATCH 2/2] KVM: x86: Defer "already loaded" check until after basic support checks Sean Christopherson
2021-10-20 14:55 ` [PATCH 0/2] KVM: x86: Enhance vendor module error messages Paolo Bonzini
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=871r4dwotz.fsf@vitty.brq.redhat.com \
--to=vkuznets@redhat.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@maciej.szmigiero.name \
--cc=pbonzini@redhat.com \
--cc=pmenzel@molgen.mpg.de \
--cc=seanjc@google.com \
--cc=wanpengli@tencent.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