From: Borislav Petkov <bp@alien8.de>
To: X86 ML <x86@kernel.org>
Cc: Feng Tang <feng.tang@intel.com>, LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH] tools/x86/kcpuid: Add AMD Secure Encryption leaf
Date: Sat, 13 Mar 2021 15:01:18 +0100 [thread overview]
Message-ID: <20210313140118.17010-1-bp@alien8.de> (raw)
From: Borislav Petkov <bp@suse.de>
Add the 0x8000001f leaf's fields.
Signed-off-by: Borislav Petkov <bp@suse.de>
---
tools/arch/x86/kcpuid/cpuid.csv | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/tools/arch/x86/kcpuid/cpuid.csv b/tools/arch/x86/kcpuid/cpuid.csv
index f4a5b85073f4..7cb5c2189345 100644
--- a/tools/arch/x86/kcpuid/cpuid.csv
+++ b/tools/arch/x86/kcpuid/cpuid.csv
@@ -378,3 +378,13 @@
0x80000008, 0, EAX, 7:0, phy_adr_bits, Physical Address Bits
0x80000008, 0, EAX, 15:8, lnr_adr_bits, Linear Address Bits
0x80000007, 0, EBX, 9, wbnoinvd, WBNOINVD
+
+# 8000001F: AMD Secure Encryption
+0x8000001F, 0, EAX, 0, SME, Secure Memory Encryption
+0x8000001F, 0, EAX, 1, SEV, Secure Encrypted Virtualization
+0x8000001F, 0, EAX, 2, VmPgFlush, VM Page Flush MSR
+0x8000001F, 0, EAX, 3, SevEs, SEV Encrypted State
+0x8000001F, 0, EBX, 5:0, C-Bit, Page table bit number used to enable memory encryption
+0x8000001F, 0, EBX, 11:6, MemEncryptPhysAddWidth, Reduction of physical address space in bits when SME is enabled
+0x8000001F, 0, ECX, 31:0, NumEncryptedGuests, Maximum ASID value that may be used for an SEV-enabled guest
+0x8000001F, 0, EDX, 31:0, MinimumSEVASID, Minimum ASID value that must be used for an SEV-enabled, SEV-ES-disabled guest
--
2.29.2
next reply other threads:[~2021-03-13 14:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-13 14:01 Borislav Petkov [this message]
2021-03-14 0:35 ` Borislav Petkov
2021-03-15 2:12 ` Feng Tang
2021-03-15 13:06 ` [tip: x86/misc] " tip-bot2 for Borislav Petkov
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=20210313140118.17010-1-bp@alien8.de \
--to=bp@alien8.de \
--cc=feng.tang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--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®