mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Feng Tang <feng.tang@intel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: X86 ML <x86@kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] tools/x86/kcpuid: Add AMD Secure Encryption leaf
Date: Mon, 15 Mar 2021 10:12:08 +0800	[thread overview]
Message-ID: <20210315021208.GA49151@shbuild999.sh.intel.com> (raw)
In-Reply-To: <20210314003527.GJ16144@zn.tnic>

On Sun, Mar 14, 2021 at 01:35:27AM +0100, Borislav Petkov wrote:
> On Sat, Mar 13, 2021 at 03:01:18PM +0100, Borislav Petkov wrote:
 
> Yeah, I guess we should keep the bit names in lowercase, for simplicity.
> 
> ---
> From: Borislav Petkov <bp@suse.de>
> Date: Sat, 13 Mar 2021 14:56:16 +0100
> Subject: [PATCH] tools/x86/kcpuid: Add AMD Secure Encryption leaf
> 
> Add the 0x8000001f leaf's fields.
> 
> Signed-off-by: Borislav Petkov <bp@suse.de>

Acked-by: Feng Tang <feng.tang@intel.com>

Thanks!

> ---
>  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..dd94c07421a8 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, mem_encrypt_physaddr_width, Reduction of physical address space in bits with SME enabled
> +0x8000001F,	0, ECX, 31:0, num_encrypted_guests, Maximum ASID value that may be used for an SEV-enabled guest
> +0x8000001F,	0, EDX, 31:0, minimum_sev_asid, Minimum ASID value that must be used for an SEV-enabled, SEV-ES-disabled guest
> -- 
> 2.29.2
> 
> -- 
> Regards/Gruss,
>     Boris.
> 
> https://people.kernel.org/tglx/notes-about-netiquette

  reply	other threads:[~2021-03-15  2:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-13 14:01 Borislav Petkov
2021-03-14  0:35 ` Borislav Petkov
2021-03-15  2:12   ` Feng Tang [this message]
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=20210315021208.GA49151@shbuild999.sh.intel.com \
    --to=feng.tang@intel.com \
    --cc=bp@alien8.de \
    --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®