From: "Zhang, Cathy" <cathy.zhang@intel.com>
To: "Hansen, Dave" <dave.hansen@intel.com>,
"linux-sgx@vger.kernel.org" <linux-sgx@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
"Raj, Ashok" <ashok.raj@intel.com>
Subject: RE: [RFC PATCH 00/11] Support microcode updates affecting SGX
Date: Thu, 10 Mar 2022 05:24:21 +0000 [thread overview]
Message-ID: <86db310117904ce99165f308227b71a7@intel.com> (raw)
In-Reply-To: <78b2e9f9-3be0-8670-a827-0a8fe7bf9ba6@intel.com>
Hi Dave, Thomas,
Thanks for helping review!
I will remove the new ABI and let microcode update process call the interface directly to clean up EPC and do EUPDATESVN. Please let me know if you have other suggestion.
> -----Original Message-----
> From: Hansen, Dave <dave.hansen@intel.com>
> Sent: Thursday, March 10, 2022 4:33 AM
> To: Zhang, Cathy <cathy.zhang@intel.com>; linux-sgx@vger.kernel.org;
> x86@kernel.org; Raj, Ashok <ashok.raj@intel.com>
> Subject: Re: [RFC PATCH 00/11] Support microcode updates affecting SGX
>
> On 3/9/22 02:40, Cathy Zhang wrote:
> > This series implements the infrastructure needed to track and tear
> > down bare-metal enclaves and then run EUPDATESVN. This is expected to
> > be triggered by administrators via sysfs at some convenient time after
> > a microcode update, probably by the microcode update tooling itself.
>
> Cathy, if it isn't abundantly clear by now, everyone seems to hate this part of
> the implementation.
>
> Let's just make this just do EUPDATESVN as a part of the microcode update
> process. No new ABI. No trying to preserve enclaves. Kill them early, kill
> them all, and be done with it.
>
> If we merge that and we have end users chasing us with torches and
> pitchforks because their precious enclaves were torn down, we'll think about
> doing something different.
prev parent reply other threads:[~2022-03-10 5:24 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 10:40 [RFC PATCH 00/11] Support microcode updates affecting SGX Cathy Zhang
2022-03-09 10:40 ` [RFC PATCH 01/11] x86/sgx: Introduce mechanism to prevent new initializations of EPC pages Cathy Zhang
2022-03-09 10:40 ` [RFC PATCH 02/11] x86/sgx: Provide VA page non-NULL owner Cathy Zhang
2022-03-09 10:40 ` [RFC PATCH 03/11] x86/sgx: Save enclave pointer for VA page Cathy Zhang
2022-03-09 10:40 ` [RFC PATCH 04/11] x86/sgx: Keep record for SGX VA and Guest page type Cathy Zhang
2022-03-09 10:40 ` [RFC PATCH 05/11] x86/sgx: Save the size of each EPC section Cathy Zhang
2022-03-09 10:40 ` [RFC PATCH 06/11] x86/sgx: Forced EPC page zapping for EUPDATESVN Cathy Zhang
2022-03-09 10:40 ` [RFC PATCH 07/11] x86/sgx: Define error codes for ENCLS[EUPDATESVN] Cathy Zhang
2022-03-09 10:40 ` [RFC PATCH 08/11] x86/sgx: Implement ENCLS[EUPDATESVN] Cathy Zhang
2022-03-09 10:40 ` [RFC PATCH 09/11] x86/microcode: Expose EUPDATESVN procedure via sysfs Cathy Zhang
2022-03-09 11:20 ` Borislav Petkov
2022-03-09 15:42 ` Dave Hansen
2022-03-09 15:48 ` Borislav Petkov
2022-03-10 5:15 ` Zhang, Cathy
2022-03-09 10:40 ` [RFC PATCH 10/11] x86/sgx: Call ENCLS[EUPDATESVN] during SGX initialization Cathy Zhang
2022-03-09 10:40 ` [RFC PATCH 11/11] Documentation/x86/sgx: Document EUPDATESVN sysfs file Cathy Zhang
2022-03-09 19:01 ` [RFC PATCH 00/11] Support microcode updates affecting SGX Thomas Gleixner
2022-03-09 19:14 ` Dave Hansen
2022-03-09 19:36 ` Borislav Petkov
2022-03-09 19:52 ` Dave Hansen
2022-03-09 20:15 ` Thomas Gleixner
2022-03-09 20:32 ` Dave Hansen
2022-03-09 20:48 ` Raj, Ashok
2022-03-09 23:09 ` Thomas Gleixner
2022-03-10 5:24 ` Zhang, Cathy [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=86db310117904ce99165f308227b71a7@intel.com \
--to=cathy.zhang@intel.com \
--cc=ashok.raj@intel.com \
--cc=dave.hansen@intel.com \
--cc=linux-sgx@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).