From: Dave Hansen <dave.hansen@intel.com>
To: "Williams, Dan J" <dan.j.williams@intel.com>,
"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
"platform-driver-x86@vger.kernel.org"
<platform-driver-x86@vger.kernel.org>,
"martin.fernandez@eclypsium.com" <martin.fernandez@eclypsium.com>
Cc: "ardb@kernel.org" <ardb@kernel.org>,
"Lutomirski, Andy" <luto@kernel.org>,
"dvhart@infradead.org" <dvhart@infradead.org>,
"Schofield, Alison" <alison.schofield@intel.com>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"hughsient@gmail.com" <hughsient@gmail.com>,
"mingo@redhat.com" <mingo@redhat.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"alex@eclypsium.com" <alex@eclypsium.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"peterz@infradead.org" <peterz@infradead.org>,
"bp@alien8.de" <bp@alien8.de>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"rafael@kernel.org" <rafael@kernel.org>,
"daniel.gutson@eclypsium.com" <daniel.gutson@eclypsium.com>,
"andy@infradead.org" <andy@infradead.org>,
"x86@kernel.org" <x86@kernel.org>
Subject: Re: [PATCH 0/5] x86: Show in sysfs if a memory node is able to do encryption
Date: Sun, 7 Nov 2021 09:58:29 -0800 [thread overview]
Message-ID: <4fb87a51-d7b8-62be-ad74-8eb08e102a1c@intel.com> (raw)
In-Reply-To: <ec77822e45be2c9736ecb6e101c5321c10b560e7.camel@intel.com>
On 11/6/21 2:35 PM, Williams, Dan J wrote:
> On Fri, 2021-11-05 at 18:27 -0300, Martin Fernandez wrote:
>> Show for each node if every memory descriptor in that node has the
>> EFI_MEMORY_CPU_CRYPTO attribute.
>
> The problem I have with EFI_MEMORY_CPU_CRYPTO is it that is vague what
> memory encryption technology is deployed and does not tell you anything
> about whether it is in effect or not.
Would this be better if it were more detailed than a binary 0/1 for
being crypto-capable? We do some pretty detailed descriptions of things
like:
> # cat /sys/devices/system/cpu/vulnerabilities/spectre_v2
> Mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling
We could do something in this case like:
# cat /sys/devices/system/node/node0/crypto_capable
Yes, EFI CPU Crypto Capable, TME active
prev parent reply other threads:[~2021-11-07 17:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-05 21:27 [PATCH 0/5] x86: Show in sysfs if a memory node is able to do encryption Martin Fernandez
2021-11-05 21:27 ` [PATCH 1/5] Extend memblock to support memory encryption Martin Fernandez
2021-11-05 23:08 ` Dave Hansen
2021-11-05 21:27 ` [PATCH 2/5] Extend pg_data_t to hold information about " Martin Fernandez
2021-11-05 23:30 ` Dave Hansen
2021-11-05 21:27 ` [PATCH 3/5] Extend e820_table " Martin Fernandez
2021-11-05 23:39 ` Dave Hansen
2021-11-08 18:40 ` Martin Fernandez
2021-11-08 21:13 ` Dave Hansen
2021-11-09 19:16 ` Martin Fernandez
2021-11-05 21:27 ` [PATCH 4/5] Mark e820_entries as crypto capable from EFI memmap Martin Fernandez
2021-11-06 0:02 ` Dave Hansen
2021-11-05 21:27 ` [PATCH 5/5] Show in sysfs if a memory node is able to do encryption Martin Fernandez
2021-11-06 0:04 ` Dave Hansen
2021-11-06 0:49 ` [PATCH 0/5] x86: " Dave Hansen
2021-11-06 21:35 ` Williams, Dan J
2021-11-07 17:58 ` Dave Hansen [this message]
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=4fb87a51-d7b8-62be-ad74-8eb08e102a1c@intel.com \
--to=dave.hansen@intel.com \
--cc=alex@eclypsium.com \
--cc=alison.schofield@intel.com \
--cc=andy@infradead.org \
--cc=ardb@kernel.org \
--cc=bp@alien8.de \
--cc=dan.j.williams@intel.com \
--cc=daniel.gutson@eclypsium.com \
--cc=dave.hansen@linux.intel.com \
--cc=dvhart@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=hughsient@gmail.com \
--cc=linux-efi@vger.kernel.org \
--cc=luto@kernel.org \
--cc=martin.fernandez@eclypsium.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=tglx@linutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).