From: "Pratik R. Sampat" <prsampat@amd.com>
To: Tom Lendacky <thomas.lendacky@amd.com>,
<linux-kernel@vger.kernel.org>, <x86@kernel.org>,
<kvm@vger.kernel.org>, <linux-crypto@vger.kernel.org>,
<linux-kselftest@vger.kernel.org>
Cc: <seanjc@google.com>, <pbonzini@redhat.com>, <tglx@linutronix.de>,
<mingo@redhat.com>, <bp@alien8.de>, <dave.hansen@linux.intel.com>,
<shuah@kernel.org>, <pgonda@google.com>, <ashish.kalra@amd.com>,
<nikunj@amd.com>, <pankaj.gupta@amd.com>, <michael.roth@amd.com>,
<sraithal@amd.com>
Subject: Re: [PATCH v7 01/10] KVM: SEV: Disable SEV-SNP support on initialization failure
Date: Tue, 25 Feb 2025 10:41:37 -0600 [thread overview]
Message-ID: <9480ce1b-2c35-499c-b60f-1c02ea9cdc16@amd.com> (raw)
In-Reply-To: <88fc49a9-d801-5d8f-f156-28fa06910cd6@amd.com>
Hi Tom,
On 2/24/2025 3:28 PM, Tom Lendacky wrote:
> On 2/21/25 15:01, Pratik R. Sampat wrote:
>> 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. Export this
>> information to KVM and withdraw SEV-SNP support if has not been
>> successfully initialized.
>
> Hmmm... rather than creating a new API, can you just issue an
> SNP_PLATFORM_STATUS command and see if the SNP is not in the UNINIT state?
>
Although reading sev->snp_initialized is probably cheaper to do, it is
cleaner to query the platform status.
Querying SNP_PLATFORM_STATUS requires the pages to transition to
firmware-owned and back, and the helpers for it are implemented within
sev-dev.c. So, similar to sev_platform_status(), I'm thinking it is
probably better to create the snp_platform_status() API as well and use
that within KVM to check the state.
Thanks!
Pratik
next prev parent reply other threads:[~2025-02-25 16:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 21:01 [PATCH v7 00/10] Basic SEV-SNP Selftests Pratik R. Sampat
2025-02-21 21:01 ` [PATCH v7 01/10] KVM: SEV: Disable SEV-SNP support on initialization failure Pratik R. Sampat
2025-02-24 19:01 ` Liam Merwick
2025-02-25 16:50 ` Pratik R. Sampat
2025-02-24 21:28 ` Tom Lendacky
2025-02-25 16:41 ` Pratik R. Sampat [this message]
2025-02-25 17:45 ` Pratik R. Sampat
2025-02-25 19:09 ` Tom Lendacky
2025-02-25 19:45 ` Pratik R. Sampat
2025-02-21 21:01 ` [PATCH v7 02/10] KVM: selftests: SEV-SNP test for KVM_SEV_INIT2 Pratik R. Sampat
2025-02-21 21:01 ` [PATCH v7 03/10] KVM: selftests: Add vmgexit helper Pratik R. Sampat
2025-02-21 21:01 ` [PATCH v7 04/10] KVM: selftests: Add SMT control state helper Pratik R. Sampat
2025-02-21 21:01 ` [PATCH v7 05/10] KVM: selftests: Replace assert() with TEST_ASSERT_EQ() Pratik R. Sampat
2025-02-21 21:01 ` [PATCH v7 06/10] KVM: selftests: Introduce SEV VM type check Pratik R. Sampat
2025-02-21 21:01 ` [PATCH v7 07/10] KVM: selftests: Add library support for interacting with SNP Pratik R. Sampat
2025-02-21 21:01 ` [PATCH v7 08/10] KVM: selftests: Force GUEST_MEMFD flag for SNP VM type Pratik R. Sampat
2025-02-21 21:01 ` [PATCH v7 09/10] KVM: selftests: Abstractions for SEV to decouple policy from type Pratik R. Sampat
2025-02-21 21:02 ` [PATCH v7 10/10] KVM: selftests: Add a basic SEV-SNP smoke test Pratik R. Sampat
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=9480ce1b-2c35-499c-b60f-1c02ea9cdc16@amd.com \
--to=prsampat@amd.com \
--cc=ashish.kalra@amd.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--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=pbonzini@redhat.com \
--cc=pgonda@google.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