From: "Pratik R. Sampat" <prsampat@amd.com>
To: <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>,
<thomas.lendacky@amd.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>, <prsampat@amd.com>
Subject: [PATCH v6 2/9] KVM: SEV: Disable SEV on platform init failure
Date: Mon, 3 Feb 2025 16:31:58 -0600 [thread overview]
Message-ID: <20250203223205.36121-3-prsampat@amd.com> (raw)
In-Reply-To: <20250203223205.36121-1-prsampat@amd.com>
If the platform initialization sev_platform_init() fails, SEV cannot be
set up and a secure VM cannot be spawned. Therefore, in this case,
ensure that KVM does not set up, nor advertise support for SEV, SEV-ES,
and SEV-SNP.
Suggested-by: Nikunj A Dadhania <nikunj@amd.com>
Tested-by: Srikanth Aithal <sraithal@amd.com>
Signed-off-by: Pratik R. Sampat <prsampat@amd.com>
---
v5..v6:
* Rename is_sev_platform_init to sev_fw_initialized (Nikunj)
* Collected tags from Srikanth.
---
arch/x86/kvm/svm/sev.c | 2 +-
drivers/crypto/ccp/sev-dev.c | 10 ++++++++++
include/linux/psp-sev.h | 3 +++
3 files changed, 14 insertions(+), 1 deletion(-)
diff --git a/arch/x86/kvm/svm/sev.c b/arch/x86/kvm/svm/sev.c
index b709c2f0945c..42d1309f8a54 100644
--- a/arch/x86/kvm/svm/sev.c
+++ b/arch/x86/kvm/svm/sev.c
@@ -2957,7 +2957,7 @@ void __init sev_hardware_setup(void)
bool sev_es_supported = false;
bool sev_supported = false;
- if (!sev_enabled || !npt_enabled || !nrips)
+ if (!sev_fw_initialized() || !sev_enabled || !npt_enabled || !nrips)
goto out;
/*
diff --git a/drivers/crypto/ccp/sev-dev.c b/drivers/crypto/ccp/sev-dev.c
index b45cd60c19b0..bd166b997ac9 100644
--- a/drivers/crypto/ccp/sev-dev.c
+++ b/drivers/crypto/ccp/sev-dev.c
@@ -81,6 +81,8 @@ MODULE_FIRMWARE("amd/amd_sev_fam19h_model1xh.sbin"); /* 4th gen EPYC */
static bool psp_dead;
static int psp_timeout;
+static bool platform_init;
+
/* Trusted Memory Region (TMR):
* The TMR is a 1MB area that must be 1MB aligned. Use the page allocator
* to allocate the memory, which will return aligned memory for the specified
@@ -1358,6 +1360,12 @@ int sev_platform_init(struct sev_platform_init_args *args)
}
EXPORT_SYMBOL_GPL(sev_platform_init);
+bool sev_fw_initialized(void)
+{
+ return platform_init;
+}
+EXPORT_SYMBOL_GPL(sev_fw_initialized);
+
static int __sev_platform_shutdown_locked(int *error)
{
struct psp_device *psp = psp_master;
@@ -2427,6 +2435,8 @@ void sev_pci_init(void)
if (rc)
dev_err(sev->dev, "SEV: failed to INIT error %#x, rc %d\n",
args.error, rc);
+ else
+ platform_init = true;
dev_info(sev->dev, "SEV%s API:%d.%d build:%d\n", sev->snp_initialized ?
"-SNP" : "", sev->api_major, sev->api_minor, sev->build);
diff --git a/include/linux/psp-sev.h b/include/linux/psp-sev.h
index e841a8fbbb15..55ef473953e3 100644
--- a/include/linux/psp-sev.h
+++ b/include/linux/psp-sev.h
@@ -946,6 +946,7 @@ void *psp_copy_user_blob(u64 uaddr, u32 len);
void *snp_alloc_firmware_page(gfp_t mask);
void snp_free_firmware_page(void *addr);
bool snp_fw_valid(void);
+bool sev_fw_initialized(void);
#else /* !CONFIG_CRYPTO_DEV_SP_PSP */
@@ -982,6 +983,8 @@ static inline void snp_free_firmware_page(void *addr) { }
static inline bool snp_fw_valid(void) { return false; }
+static inline bool sev_fw_initialized(void) { return false; }
+
#endif /* CONFIG_CRYPTO_DEV_SP_PSP */
#endif /* __PSP_SEV_H__ */
--
2.43.0
next prev parent reply other threads:[~2025-02-03 22:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 22:31 [PATCH v6 0/9] Basic SEV-SNP Selftests Pratik R. Sampat
2025-02-03 22:31 ` [PATCH v6 1/9] KVM: SEV: Disable SEV-SNP on FW validation failure Pratik R. Sampat
2025-02-12 1:54 ` Sean Christopherson
2025-02-14 18:07 ` Pratik Rajesh Sampat
2025-02-03 22:31 ` Pratik R. Sampat [this message]
2025-02-12 1:58 ` [PATCH v6 2/9] KVM: SEV: Disable SEV on platform init failure Sean Christopherson
2025-02-14 18:09 ` Pratik Rajesh Sampat
2025-02-03 22:31 ` [PATCH v6 3/9] KVM: selftests: SEV-SNP test for KVM_SEV_INIT2 Pratik R. Sampat
2025-02-03 22:32 ` [PATCH v6 4/9] KVM: selftests: Add VMGEXIT helper Pratik R. Sampat
2025-02-12 1:59 ` Sean Christopherson
2025-02-14 18:09 ` Pratik Rajesh Sampat
2025-02-03 22:32 ` [PATCH v6 5/9] KVM: selftests: Introduce SEV VM type check Pratik R. Sampat
2025-02-03 22:32 ` [PATCH v6 6/9] KVM: selftests: Add library support for interacting with SNP Pratik R. Sampat
2025-02-12 2:12 ` Sean Christopherson
2025-02-14 18:12 ` Pratik Rajesh Sampat
2025-02-19 16:55 ` Sean Christopherson
2025-02-20 16:56 ` Pratik Rajesh Sampat
2025-02-03 22:32 ` [PATCH v6 7/9] KVM: selftests: Force GUEST_MEMFD flag for SNP VM type Pratik R. Sampat
2025-02-03 22:32 ` [PATCH v6 8/9] KVM: selftests: Abstractions for SEV to decouple policy from type Pratik R. Sampat
2025-02-03 22:32 ` [PATCH v6 9/9] KVM: selftests: Add a basic SEV-SNP smoke test Pratik R. Sampat
2025-02-12 2:31 ` Sean Christopherson
2025-02-14 18:14 ` Pratik Rajesh Sampat
2025-02-19 0:54 ` Sean Christopherson
2025-02-19 14:58 ` Pratik Rajesh 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=20250203223205.36121-3-prsampat@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