From: Dave Hansen <dave.hansen@intel.com>
To: Jethro Beekman <jethro@fortanix.com>,
Cathy Zhang <cathy.zhang@intel.com>,
linux-sgx@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: ashok.raj@intel.com
Subject: Re: [RFC PATCH v2 09/10] x86/cpu: Call ENCLS[EUPDATESVN] procedure in microcode update
Date: Wed, 16 Mar 2022 08:47:23 -0700 [thread overview]
Message-ID: <e121e972-7689-b2f3-5919-746e3a90cb36@intel.com> (raw)
In-Reply-To: <e1682971-4821-8e57-3232-de7a72086991@fortanix.com>
On 3/16/22 03:24, Jethro Beekman wrote:
>> Doing this automatically and unconditionally during a microcode
>> update seems undesirable. This requires the userland tooling that
>> is coordinating the microcode update to be aware of any SGX
>> enclaves that are running and possibly coordinate sequencing with
>> the processes containing those enclaves. This coupling does not
>> exist today.
> Also, a microcode update may not affect SGX security at all and doing
> the EUPDATESVN procedure may not be required for this particular
> update. This case is called out specifically in the EUPDATESVN
> documentation.
I don't think Intel provides the metadata for the kernel to tell if an
update requires an EUPDATESVN procedure or not. If this is inconvenient
for you, I'd suggest reporting this to the folks at Intel who can fix
it. It doesn't seem like something which they are motivated to fix.
next prev parent reply other threads:[~2022-03-16 15:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 1:02 [RFC PATCH v2 00/10] Support microcode updates affecting SGX Cathy Zhang
2022-03-15 1:02 ` [RFC PATCH v2 01/10] x86/sgx: Introduce mechanism to prevent new initializations of EPC pages Cathy Zhang
2022-03-17 4:12 ` Jarkko Sakkinen
2022-03-17 14:08 ` Zhang, Cathy
2022-03-17 18:52 ` Jarkko Sakkinen
2022-03-18 2:33 ` Zhang, Cathy
2022-03-18 16:23 ` Reinette Chatre
2022-03-22 1:11 ` Zhang, Cathy
2022-03-15 1:02 ` [RFC PATCH v2 02/10] x86/sgx: Provide VA page non-NULL owner Cathy Zhang
2022-03-15 1:02 ` [RFC PATCH v2 03/10] x86/sgx: Save enclave pointer for VA page Cathy Zhang
2022-03-15 1:02 ` [RFC PATCH v2 04/10] x86/sgx: Keep record for SGX VA and Guest page type Cathy Zhang
2022-03-15 1:02 ` [RFC PATCH v2 05/10] x86/sgx: Save the size of each EPC section Cathy Zhang
2022-03-15 1:02 ` [RFC PATCH v2 06/10] x86/sgx: Forced EPC page zapping for EUPDATESVN Cathy Zhang
2022-03-15 1:02 ` [RFC PATCH v2 07/10] x86/sgx: Define error codes for ENCLS[EUPDATESVN] Cathy Zhang
2022-03-15 1:02 ` [RFC PATCH v2 08/10] x86/sgx: Implement ENCLS[EUPDATESVN] Cathy Zhang
2022-03-15 1:02 ` [RFC PATCH v2 09/10] x86/cpu: Call ENCLS[EUPDATESVN] procedure in microcode update Cathy Zhang
2022-03-16 9:46 ` Jethro Beekman
2022-03-16 10:24 ` Jethro Beekman
2022-03-16 15:47 ` Dave Hansen [this message]
2022-03-18 9:06 ` Jethro Beekman
2022-03-22 1:35 ` Zhang, Cathy
2022-03-16 15:42 ` Dave Hansen
2022-03-18 9:04 ` Jethro Beekman
2022-03-15 1:03 ` [RFC PATCH v2 10/10] x86/sgx: Call ENCLS[EUPDATESVN] during SGX initialization Cathy Zhang
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=e121e972-7689-b2f3-5919-746e3a90cb36@intel.com \
--to=dave.hansen@intel.com \
--cc=ashok.raj@intel.com \
--cc=cathy.zhang@intel.com \
--cc=jethro@fortanix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sgx@vger.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®