From: Sean Christopherson <seanjc@google.com>
To: Alexander Mikhalitsyn <aleksandr.mikhalitsyn@canonical.com>
Cc: pbonzini@redhat.com, "Stéphane Graber" <stgraber@ubuntu.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
"Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@redhat.com>,
"Borislav Petkov" <bp@alien8.de>,
"Dave Hansen" <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH v2 2/2] KVM: SVM: enhance info printk's in SEV init
Date: Tue, 6 Jun 2023 11:46:38 -0700 [thread overview]
Message-ID: <ZH9/Drgo+sDYTGIG@google.com> (raw)
In-Reply-To: <20230522161249.800829-3-aleksandr.mikhalitsyn@canonical.com>
On Mon, May 22, 2023, Alexander Mikhalitsyn wrote:
> diff --git a/arch/x86/kvm/svm/sev.c b/arch/x86/kvm/svm/sev.c
> index cc832a8d1bca..fff63d1f2a34 100644
> --- a/arch/x86/kvm/svm/sev.c
> +++ b/arch/x86/kvm/svm/sev.c
> @@ -2224,7 +2224,6 @@ void __init sev_hardware_setup(void)
> goto out;
> }
>
> - pr_info("SEV supported: %u ASIDs\n", sev_asid_count);
> sev_supported = true;
>
> /* SEV-ES support requested? */
> @@ -2252,10 +2251,16 @@ void __init sev_hardware_setup(void)
> if (misc_cg_set_capacity(MISC_CG_RES_SEV_ES, sev_es_asid_count))
> goto out;
>
> - pr_info("SEV-ES supported: %u ASIDs\n", sev_es_asid_count);
> sev_es_supported = true;
>
> out:
> + if (boot_cpu_has(X86_FEATURE_SEV))
> + pr_info("SEV %s (ASIDs %u - %u)\n",
> + sev_supported ? "enabled" : "disabled", min_sev_asid, max_sev_asid);
> + if (boot_cpu_has(X86_FEATURE_SEV_ES))
> + pr_info("SEV-ES %s (ASIDs %u - %u)\n",
> + sev_es_supported ? "enabled" : "disabled", 1, min_sev_asid - 1);
The min should print '0' if min_sev_asid<=1, otherwise the output will be
SEV-ES disabled (ASIDs 1 - 0)
which is confusing. That would also align with what gets printed out for SEV
when it's not supported at all (min==max=0).
No need for v3, I'll fixup when applying.
next prev parent reply other threads:[~2023-06-06 18:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 16:12 [PATCH v2 0/2] KVM: SVM: small tweaks for sev_hardware_setup Alexander Mikhalitsyn
2023-05-22 16:12 ` [PATCH v2 1/2] KVM: SVM: free sev_*asid_bitmap init if SEV init fails Alexander Mikhalitsyn
2023-06-06 18:45 ` Sean Christopherson
2023-06-06 18:51 ` Aleksandr Mikhalitsyn
2023-05-22 16:12 ` [PATCH v2 2/2] KVM: SVM: enhance info printk's in SEV init Alexander Mikhalitsyn
2023-06-06 18:46 ` Sean Christopherson [this message]
2023-06-06 18:52 ` Aleksandr Mikhalitsyn
2023-06-06 18:48 ` [PATCH v2 0/2] KVM: SVM: small tweaks for sev_hardware_setup 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=ZH9/Drgo+sDYTGIG@google.com \
--to=seanjc@google.com \
--cc=aleksandr.mikhalitsyn@canonical.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=stgraber@ubuntu.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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.