From: Dave Hansen <dave.hansen@intel.com>
To: Martin Fernandez <martin.fernandez@eclypsium.com>,
linux-efi@vger.kernel.org, platform-driver-x86@vger.kernel.org
Cc: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
x86@kernel.org, hpa@zytor.com, dave.hansen@linux.intel.com,
luto@kernel.org, peterz@infradead.org, ardb@kernel.org,
dvhart@infradead.org, andy@infradead.org,
gregkh@linuxfoundation.org, rafael@kernel.org,
daniel.gutson@eclypsium.com, hughsient@gmail.com
Subject: Re: [PATCH v2 5/5] Show in sysfs if a memory node is able to do memory encryption
Date: Thu, 28 Oct 2021 11:09:51 -0700 [thread overview]
Message-ID: <18bd9cc5-f275-1e56-98ea-bd67073f7e4b@intel.com> (raw)
In-Reply-To: <20211027195511.207552-6-martin.fernandez@eclypsium.com>
On 10/27/21 12:55 PM, Martin Fernandez wrote:
> This value will only be shown if the memory is local to at least one
> CPU, since otherwise it won't be able to be encrypted by CPU's
> cryptographic capabilities. This check is done against the ACPI's SRAT
> table.
What does "local to at least one CPU" mean? I can't even make sense of
what the code is trying to do (which is a whole separate issue).
next prev parent reply other threads:[~2021-10-28 18:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 19:55 [PATCH v2 0/5] [RFC] x86: Export information about hardware memory encryption to sysfs Martin Fernandez
2021-10-27 19:55 ` [PATCH v2 1/5] Extend memblock to support memory encryption Martin Fernandez
2021-10-27 19:55 ` [PATCH v2 2/5] Extend pg_data_t to hold information about " Martin Fernandez
2021-10-27 19:55 ` [PATCH v2 3/5] Extend e820_table " Martin Fernandez
2021-10-27 19:55 ` [PATCH v2 4/5] Mark e820_entries as crypto capable from EFI memmap Martin Fernandez
2021-10-27 19:55 ` [PATCH v2 5/5] Show in sysfs if a memory node is able to do memory encryption Martin Fernandez
2021-10-28 18:09 ` Dave Hansen [this message]
2021-10-27 20:21 ` [PATCH v2 0/5] [RFC] x86: Export information about hardware memory encryption to sysfs Dave Hansen
2021-10-28 14:28 ` Martin Fernandez
2021-10-28 14:55 ` Borislav Petkov
2021-10-28 16:03 ` Richard Hughes
2021-10-28 16:35 ` Borislav Petkov
2021-10-28 17:39 ` Martin Fernandez
2021-10-28 18:10 ` Borislav Petkov
2021-10-28 18:17 ` Dave Hansen
2021-10-29 17:08 ` Dave Hansen
2021-11-01 18:12 ` Martin Fernandez
2021-11-01 20:10 ` Martin Fernandez
2021-10-29 13:14 ` Richard Hughes
2021-10-28 15:24 ` Dave Hansen
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=18bd9cc5-f275-1e56-98ea-bd67073f7e4b@intel.com \
--to=dave.hansen@intel.com \
--cc=andy@infradead.org \
--cc=ardb@kernel.org \
--cc=bp@alien8.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.