From: Dave Hansen <dave.hansen@intel.com>
To: Daniel Gutson <daniel.gutson@eclypsium.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Peter Zijlstra <peterz@infradead.org>
Cc: "David S. Miller" <davem@davemloft.net>,
Rob Herring <robh@kernel.org>, Tony Luck <tony.luck@intel.com>,
Rahul Tanwar <rahul.tanwar@linux.intel.com>,
Xiaoyao Li <xiaoyao.li@intel.com>,
Sean Christopherson <sean.j.christopherson@intel.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Ability to read the MKTME status from userspace (patch v2)
Date: Thu, 25 Jun 2020 14:29:11 -0700 [thread overview]
Message-ID: <06a5f311-9084-74da-9263-a35a9779f622@intel.com> (raw)
In-Reply-To: <20200625211029.34733-1-daniel.gutson@eclypsium.com>
On 6/25/20 2:10 PM, Daniel Gutson wrote:
> The intent of this patch is to provide visibility of the
> MKTME status to userspace. This is an important factor for
> firmware security related applilcations.
We need more specifics than this. It's an important factor for what,
exactly? Who will consume this and what will they do with it?
I'm also not sure we want to have an Intel product name in the ABI. If
we're meaning to tell folks if hardware memory encryption is available
on the platform, let's say _that_, rather than talk about MKTME.
Also, MKTME enabling isn't all that interesting. TME is much more
interesting and much more opaque.
next prev parent reply other threads:[~2020-06-25 21:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-25 21:10 Daniel Gutson
2020-06-25 21:14 ` Borislav Petkov
[not found] ` <CAFmMkTGy5vOiPUpWw6HfQv-JM90JqLBcsKwMpbWdsjaLBw730Q@mail.gmail.com>
2020-06-25 21:27 ` Borislav Petkov
2020-06-25 21:37 ` Dave Hansen
2020-06-25 21:39 ` Andy Lutomirski
2020-06-25 21:43 ` Dave Hansen
2020-06-25 21:29 ` Dave Hansen [this message]
2020-06-26 1:55 ` Alison Schofield
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=06a5f311-9084-74da-9263-a35a9779f622@intel.com \
--to=dave.hansen@intel.com \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=daniel.gutson@eclypsium.com \
--cc=dave.hansen@linux.intel.com \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rahul.tanwar@linux.intel.com \
--cc=robh@kernel.org \
--cc=sean.j.christopherson@intel.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
--cc=xiaoyao.li@intel.com \
/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®