From: Zhiquan Li <zhiquan1.li@intel.com>
To: "Luck, Tony" <tony.luck@intel.com>, Jarkko Sakkinen <jarkko@kernel.org>
Cc: "linux-sgx@vger.kernel.org" <linux-sgx@vger.kernel.org>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"Christopherson,, Sean" <seanjc@google.com>,
"Du, Fan" <fan.du@intel.com>, <zhiquan1.li@intel.com>
Subject: Re: [PATCH 0/4] x86/sgx: fine grained SGX MCA behavior
Date: Mon, 16 May 2022 08:57:29 +0800 [thread overview]
Message-ID: <b5232de5-d3c4-892a-12af-983c3dc4c9ae@intel.com> (raw)
In-Reply-To: <5b6ad3e2af614caf9b41092797ffcd86@intel.com>
On 2022/5/15 11:35, Luck, Tony wrote:
>> Any machine check exception (#MC) that occurs after Intel SGX is first enables
>> causes Intel SGX to be disabled, (CPUID.SGX_Leaf.0:EAX[SGX1] == 0). It cannot be
>> enabled until after the next reset. "
>
> That part is out of date. A machine check used to disable SGX system-wide. It now just
> disables the enclave that triggered the machine check.
>
> Is that text still in the latest SDM (version 077, April 2022)?
Yes, I've double checked it, version 077, Apr. 2022.
Looks like SDM needs to follow up :-)
Best Regards,
Zhiquan
>
> -Tony
next prev parent reply other threads:[~2022-05-16 0:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 3:16 [PATCH 0/4] x86/sgx: fine grained SGX MCA behavior Zhiquan Li
2022-05-11 10:29 ` Jarkko Sakkinen
2022-05-12 12:03 ` Zhiquan Li
2022-05-13 14:38 ` Jarkko Sakkinen
2022-05-13 16:35 ` Luck, Tony
2022-05-14 5:39 ` Zhiquan Li
2022-05-15 3:35 ` Luck, Tony
2022-05-16 0:57 ` Zhiquan Li [this message]
2022-05-16 2:29 ` Kai Huang
2022-05-16 8:40 ` Zhiquan Li
2022-05-17 0:43 ` Kai Huang
2022-05-18 1:02 ` Zhiquan Li
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=b5232de5-d3c4-892a-12af-983c3dc4c9ae@intel.com \
--to=zhiquan1.li@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=fan.du@intel.com \
--cc=jarkko@kernel.org \
--cc=linux-sgx@vger.kernel.org \
--cc=seanjc@google.com \
--cc=tony.luck@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