From: "Luck, Tony" <tony.luck@intel.com>
To: Jarkko Sakkinen <jarkko@kernel.org>,
"Li, Zhiquan1" <zhiquan1.li@intel.com>
Cc: "linux-sgx@vger.kernel.org" <linux-sgx@vger.kernel.org>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"seanjc@google.com" <seanjc@google.com>,
"Du, Fan" <fan.du@intel.com>
Subject: RE: [PATCH 0/4] x86/sgx: fine grained SGX MCA behavior
Date: Fri, 13 May 2022 16:35:36 +0000 [thread overview]
Message-ID: <55ffd9475f5d46f68dd06c4323bec871@intel.com> (raw)
In-Reply-To: <Yn5tPS0aLXBgHtYT@iki.fi>
>> Do you think the processes sharing the same enclave need to be killed,
>> even they had not touched the EPC page with hardware error?
>> Any ideas are welcome.
>
> I do not think the patch set is going to wrong direction. This discussion
> was just missing from the cover letter.
I was under the impression that when an enclave page triggers a machine check
the whole enclave is (somehow) marked bad, so that it couldn't be entered again.
Killing other processes with the same enclave mapped would perhaps be overkill,
but they are going to find that the enclave is "dead" next time they try to use it.
-Tony
next prev parent reply other threads:[~2022-05-13 16:35 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 [this message]
2022-05-14 5:39 ` Zhiquan Li
2022-05-15 3:35 ` Luck, Tony
2022-05-16 0:57 ` Zhiquan Li
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=55ffd9475f5d46f68dd06c4323bec871@intel.com \
--to=tony.luck@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=zhiquan1.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