From: Jack Wang <jinpu.wang@ionos.com>
To: gregkh@linuxfoundation.org, sashal@kernel.org, stable@vger.kernel.org
Cc: dmitrii.omelchenko@cloud.ionos.com,
Ashish Kalra <ashish.kalra@amd.com>,
Sean Christopherson <seanjc@google.com>,
Tom Lendacky <thomas.lendacky@amd.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Jack Wang <jinpu.wang@cloud.ionos.com>
Subject: [stable-6.12 2/4] KVM: SVM: Add support to initialize SEV/SNP functionality in KVM
Date: Fri, 14 Aug 2026 12:02:55 +0200 [thread overview]
Message-ID: <20260814100652.225499-3-jinpu.wang@ionos.com> (raw)
In-Reply-To: <20260814100652.225499-1-jinpu.wang@ionos.com>
From: Ashish Kalra <ashish.kalra@amd.com>
commit 6f1d5a3513c2370bbd6115dd430906bc2f4bdc53 upstream.
Move platform initialization of SEV/SNP from CCP driver probe time to
KVM module load time so that KVM can do SEV/SNP platform initialization
explicitly if it actually wants to use SEV/SNP functionality.
Add support for KVM to explicitly call into the CCP driver at load time
to initialize SEV/SNP. If required, this behavior can be altered with KVM
module parameters to not do SEV/SNP platform initialization at module load
time. Additionally, a corresponding SEV/SNP platform shutdown is invoked
during KVM module unload time.
Continue to support SEV deferred initialization as the user may have the
file containing SEV persistent data for SEV INIT_EX available only later
after module load/init.
Suggested-by: Sean Christopherson <seanjc@google.com>
Reviewed-by: Tom Lendacky <thomas.lendacky@amd.com>
Signed-off-by: Ashish Kalra <ashish.kalra@amd.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Signed-off-by: Jack Wang <jinpu.wang@cloud.ionos.com>
---
arch/x86/kvm/svm/sev.c | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/arch/x86/kvm/svm/sev.c b/arch/x86/kvm/svm/sev.c
index 6cec696461da..bd0344bacaf1 100644
--- a/arch/x86/kvm/svm/sev.c
+++ b/arch/x86/kvm/svm/sev.c
@@ -2972,6 +2972,7 @@ void __init sev_set_cpu_caps(void)
void __init sev_hardware_setup(void)
{
unsigned int eax, ebx, ecx, edx, sev_asid_count, sev_es_asid_count;
+ struct sev_platform_init_args init_args = {0};
bool sev_snp_supported = false;
bool sev_es_supported = false;
bool sev_supported = false;
@@ -3088,6 +3089,15 @@ 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)
@@ -3103,6 +3113,8 @@ void sev_hardware_unsetup(void)
misc_cg_set_capacity(MISC_CG_RES_SEV, 0);
misc_cg_set_capacity(MISC_CG_RES_SEV_ES, 0);
+
+ sev_platform_shutdown();
}
int sev_cpu_init(struct svm_cpu_data *sd)
--
2.43.0
next prev parent reply other threads:[~2026-08-14 10:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 10:02 [PATCH 6.12.y 0/4] crypto: ccp, KVM: SVM - missing SEV/SNP platform-init dependency + 2 bugfixes Jack Wang
2026-08-14 10:02 ` [stable-6.12 1/4] crypto: ccp - Add new SEV/SNP platform shutdown API Jack Wang
2026-08-14 10:02 ` Jack Wang [this message]
2026-08-14 14:40 ` [stable-6.12 2/4] KVM: SVM: Add support to initialize SEV/SNP functionality in KVM Sean Christopherson
2026-08-14 10:02 ` [stable-6.12 3/4] crypto: ccp - Fix checks for SNP_VLEK_LOAD input buffer length Jack Wang
2026-08-14 10:02 ` [stable-6.12 4/4] crypto: ccp - Abort doing SEV INIT if SNP INIT fails Jack Wang
2026-08-15 2:33 ` [PATCH 6.12.y 0/4] crypto: ccp, KVM: SVM - missing SEV/SNP platform-init dependency + 2 bugfixes Sasha Levin
2026-08-17 4:51 ` Jinpu Wang
2026-08-17 5:00 ` Greg KH
2026-08-17 5:22 ` Jinpu Wang
2026-08-17 5:34 ` Greg KH
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=20260814100652.225499-3-jinpu.wang@ionos.com \
--to=jinpu.wang@ionos.com \
--cc=ashish.kalra@amd.com \
--cc=dmitrii.omelchenko@cloud.ionos.com \
--cc=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=jinpu.wang@cloud.ionos.com \
--cc=sashal@kernel.org \
--cc=seanjc@google.com \
--cc=stable@vger.kernel.org \
--cc=thomas.lendacky@amd.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