From: "Paluri, PavanKumar" <papaluri@amd.com>
To: Ashish Kalra <Ashish.Kalra@amd.com>,
seanjc@google.com, pbonzini@redhat.com, tglx@linutronix.de,
mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
thomas.lendacky@amd.com, shuah@kernel.org, prsampat@amd.com
Cc: pgonda@google.com, nikunj@amd.com, pankaj.gupta@amd.com,
michael.roth@amd.com, sraithal@amd.com,
linux-kernel@vger.kernel.org, x86@kernel.org,
kvm@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-coco@lists.linux.dev, "Paluri,
PavanKumar (Pavan Kumar)" <pavankumar.paluri@amd.com>
Subject: Re: [PATCH v3] KVM: SEV: Disable SEV-SNP support on initialization failure
Date: Mon, 12 May 2025 18:07:10 -0500 [thread overview]
Message-ID: <708cfa2d-0a5a-4f83-bf43-97a63a8ae4ea@amd.com> (raw)
In-Reply-To: <20250512221634.12045-1-Ashish.Kalra@amd.com>
On 5/12/2025 5:16 PM, Ashish Kalra wrote:
> From: Ashish Kalra <ashish.kalra@amd.com>
>
> During platform init, SNP initialization may fail for several reasons,
> such as firmware command failures and incompatible versions. However,
> the KVM capability may continue to advertise support for it.
>
> The platform may have SNP enabled but if SNP_INIT fails then SNP is
> not supported by KVM.
>
> During KVM module initialization query the SNP platform status to obtain
> the SNP initialization state and use it as an additional condition to
> determine support for SEV-SNP.
>
> Co-developed-by: Sean Christopherson <seanjc@google.com>
> Signed-off-by: Sean Christopherson <seanjc@google.com>
> Co-developed-by: Pratik R. Sampat <prsampat@amd.com>
> Signed-off-by: Pratik R. Sampat <prsampat@amd.com>
> Reviewed-by: Tom Lendacky <thomas.lendacky@amd.com>
> Signed-off-by: Ashish Kalra <ashish.kalra@amd.com>
Reviewed-by: Pavan Kumar Paluri <papaluri@amd.com>
Thanks,
Pavan
> ---
> arch/x86/kvm/svm/sev.c | 44 +++++++++++++++++++++++++++++++++---------
> 1 file changed, 35 insertions(+), 9 deletions(-)
>
> diff --git a/arch/x86/kvm/svm/sev.c b/arch/x86/kvm/svm/sev.c
> index dea9480b9ff6..8c3b12e3de8c 100644
> --- a/arch/x86/kvm/svm/sev.c
> +++ b/arch/x86/kvm/svm/sev.c
> @@ -2935,6 +2935,33 @@ void __init sev_set_cpu_caps(void)
> }
> }
>
> +static bool is_sev_snp_initialized(void)
> +{
> + struct sev_user_data_snp_status *status;
> + struct sev_data_snp_addr buf;
> + bool initialized = false;
> + int ret, error = 0;
> +
> + status = snp_alloc_firmware_page(GFP_KERNEL | __GFP_ZERO);
> + if (!status)
> + return false;
> +
> + buf.address = __psp_pa(status);
> + ret = sev_do_cmd(SEV_CMD_SNP_PLATFORM_STATUS, &buf, &error);
> + if (ret) {
> + pr_err("SEV: SNP_PLATFORM_STATUS failed ret=%d, fw_error=%d (%#x)\n",
> + ret, error, error);
> + goto out;
> + }
> +
> + initialized = !!status->state;
> +
> +out:
> + snp_free_firmware_page(status);
> +
> + return initialized;
> +}
> +
> void __init sev_hardware_setup(void)
> {
> unsigned int eax, ebx, ecx, edx, sev_asid_count, sev_es_asid_count;
> @@ -3039,6 +3066,14 @@ void __init sev_hardware_setup(void)
> sev_snp_supported = sev_snp_enabled && cc_platform_has(CC_ATTR_HOST_SEV_SNP);
>
> out:
> + if (sev_enabled) {
> + init_args.probe = true;
> + if (sev_platform_init(&init_args))
> + sev_supported = sev_es_supported = sev_snp_supported = false;
> + else if (sev_snp_supported)
> + sev_snp_supported = is_sev_snp_initialized();
> + }
> +
> if (boot_cpu_has(X86_FEATURE_SEV))
> pr_info("SEV %s (ASIDs %u - %u)\n",
> sev_supported ? min_sev_asid <= max_sev_asid ? "enabled" :
> @@ -3065,15 +3100,6 @@ void __init sev_hardware_setup(void)
> sev_supported_vmsa_features = 0;
> if (sev_es_debug_swap_enabled)
> sev_supported_vmsa_features |= SVM_SEV_FEAT_DEBUG_SWAP;
> -
> - if (!sev_enabled)
> - return;
> -
> - /*
> - * Do both SNP and SEV initialization at KVM module load.
> - */
> - init_args.probe = true;
> - sev_platform_init(&init_args);
> }
>
> void sev_hardware_unsetup(void)
next prev parent reply other threads:[~2025-05-12 23:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 22:16 [PATCH v3] KVM: SEV: Disable SEV-SNP support on initialization failure Ashish Kalra
2025-05-12 23:07 ` Paluri, PavanKumar [this message]
2025-05-13 4:46 ` Gupta, Pankaj
2025-05-19 19:10 ` Kalra, Ashish
2025-06-11 18:27 ` 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=708cfa2d-0a5a-4f83-bf43-97a63a8ae4ea@amd.com \
--to=papaluri@amd.com \
--cc=Ashish.Kalra@amd.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=michael.roth@amd.com \
--cc=mingo@redhat.com \
--cc=nikunj@amd.com \
--cc=pankaj.gupta@amd.com \
--cc=pavankumar.paluri@amd.com \
--cc=pbonzini@redhat.com \
--cc=pgonda@google.com \
--cc=prsampat@amd.com \
--cc=seanjc@google.com \
--cc=shuah@kernel.org \
--cc=sraithal@amd.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).