From: Mario Limonciello <mario.limonciello@amd.com>
To: Borislav Petkov <bp@alien8.de>,
"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<x86@kernel.org>
Cc: Kees Cook <keescook@chromium.org>,
Thomas Lendacky <Thomas.Lendacky@amd.com>, <hughsient@gmail.com>,
Martin Fernandez <martin.fernandez@eclypsium.com>,
<linux-kernel@vger.kernel.org>,
"Brijesh Singh" <brijesh.singh@amd.com>,
Mario Limonciello <mario.limonciello@amd.com>
Subject: [PATCH v2 1/4] crypto: ccp: Use cc_platform_has to determine SEV presence
Date: Fri, 11 Feb 2022 15:02:52 -0600 [thread overview]
Message-ID: <20220211210255.9820-2-mario.limonciello@amd.com> (raw)
In-Reply-To: <20220211210255.9820-1-mario.limonciello@amd.com>
The CPU feature flag shouldn't be used to determine if SEV is active,
that's what `cc_platform_has` is for.
Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
---
drivers/crypto/ccp/sev-dev.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/crypto/ccp/sev-dev.c b/drivers/crypto/ccp/sev-dev.c
index 8fd774a10edc..e061eb6a039c 100644
--- a/drivers/crypto/ccp/sev-dev.c
+++ b/drivers/crypto/ccp/sev-dev.c
@@ -1148,7 +1148,7 @@ int sev_dev_init(struct psp_device *psp)
struct sev_device *sev;
int ret = -ENOMEM;
- if (!boot_cpu_has(X86_FEATURE_SEV)) {
+ if (!cc_platform_has(CC_ATTR_GUEST_MEM_ENCRYPT)) {
dev_info_once(dev, "SEV: memory encryption not enabled by BIOS\n");
return 0;
}
--
2.34.1
next prev parent reply other threads:[~2022-02-11 21:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 21:02 [PATCH v2 0/4] Only export SME/SEV/SEV_ES features when activated Mario Limonciello
2022-02-11 21:02 ` Mario Limonciello [this message]
2022-02-11 21:02 ` [PATCH v2 2/4] KVM: SVM: Use cc_platform_has instead of CPU feature flags Mario Limonciello
2022-02-11 21:02 ` [PATCH v2 3/4] x86/cpu: clear SME features when not in use Mario Limonciello
2022-02-11 21:17 ` Tom Lendacky
2022-02-11 21:02 ` [PATCH v2 4/4] x86/cpu: clear SEV/SEV_ES " Mario Limonciello
2022-02-11 21:13 ` [PATCH v2 0/4] Only export SME/SEV/SEV_ES features when activated Tom Lendacky
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=20220211210255.9820-2-mario.limonciello@amd.com \
--to=mario.limonciello@amd.com \
--cc=Thomas.Lendacky@amd.com \
--cc=bp@alien8.de \
--cc=brijesh.singh@amd.com \
--cc=hughsient@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.fernandez@eclypsium.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
all inboxes | Powered by JetHome®