From: "Luck, Tony" <tony.luck@intel.com>
To: Jarkko Sakkinen <jarkko@kernel.org>,
"Li, Zhiquan1" <zhiquan1.li@intel.com>,
"Huang, Kai" <kai.huang@intel.com>, "Du, Fan" <fan.du@intel.com>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"linux-sgx@vger.kernel.org" <linux-sgx@vger.kernel.org>,
"Hansen, Dave" <dave.hansen@intel.com>,
"Zhang, Cathy" <cathy.zhang@intel.com>
Cc: "Christopherson,, Sean" <seanjc@google.com>
Subject: RE: [PATCH v3 0/3] x86/sgx: fine grained SGX MCA behavior
Date: Tue, 7 Jun 2022 15:43:34 +0000 [thread overview]
Message-ID: <e1c78d1a31234384a005736115906127@intel.com> (raw)
In-Reply-To: <41704e5d4c03b49fcda12e695595211d950cfb08.camel@kernel.org>
> I think Tony hinted me about mechanism to test MCA behaviour in
> kernel but I cannot recall it anymore. Was there a way to make
> to simulate a memory failure, and use that to test the patch
> set?
It is possible to inject real errors into enclave memory using ACPI/EINJ.
See the final part of:
Documentation/firmware-guide/acpi/apei/einj.rst
You do a faked test by just asking to offline a page:
# echo {pfn} > /sys/devices/system/memory/hard_offline_page
-Tony
next prev parent reply other threads:[~2022-06-07 15:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 10:06 [PATCH v3 0/3] x86/sgx: fine grained SGX MCA behavior Zhiquan Li
2022-05-26 0:35 ` Jarkko Sakkinen
2022-06-03 1:15 ` Du, Fan
2022-06-06 10:40 ` Kai Huang
2022-06-07 6:35 ` Jarkko Sakkinen
2022-06-07 7:02 ` Zhiquan Li
2022-06-07 8:26 ` Jarkko Sakkinen
2022-06-07 15:43 ` Luck, Tony [this message]
2022-06-08 0:19 ` Jarkko Sakkinen
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=e1c78d1a31234384a005736115906127@intel.com \
--to=tony.luck@intel.com \
--cc=cathy.zhang@intel.com \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=fan.du@intel.com \
--cc=jarkko@kernel.org \
--cc=kai.huang@intel.com \
--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