From: Thomas Tai <thomas.tai@oracle.com>
To: tony.luck@intel.com, dave.hansen@linux.intel.com,
jarkko@kernel.org, reinette.chatre@intel.com,
linmiaohe@huawei.com, akpm@linux-foundation.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
naoya.horiguchi@nec.com, thomas.tai@oracle.com
Subject: [PATCH V3 0/1] x86/sgx: Add code to inject hwpoison into SGX memory
Date: Mon, 17 Oct 2022 18:33:04 -0400 [thread overview]
Message-ID: <20221017223305.578073-1-thomas.tai@oracle.com> (raw)
This patch adds code to inject hwpoison into SGX memory. The SGX memory
is processor reserved memory that cannot be directly accessed by system
software.
Changes since v2:
- As suggested by Naoya Horiguchi <naoya.horiguchi@nec.com>, add a
new mf_action_page_type MF_MSG_SGX and use action_result() to
show the page type and the action taken.
- Rewrite hwpoison.rst to show the output from dmesg after injection.
- Add reinette.chatre@intel.com to the email list. Sorry that I
mistyped the email address in the previous emails.
- v2 Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
Changes since v1:
- Add a comment in hwpoison_inject as suggested by Miaohe
- v1: Reviewed-by: Tony Luck <tony.luck@intel.com>
- v1: Reviewed-by: Miaohe Lin <linmiaohe@huawei.com>
Thomas Tai (1):
x86/sgx: Add code to inject hwpoison into SGX memory
Documentation/mm/hwpoison.rst | 24 ++++++++++++++++++++++++
include/linux/mm.h | 1 +
include/ras/ras_event.h | 1 +
mm/hwpoison-inject.c | 4 ++++
mm/memory-failure.c | 5 ++++-
5 files changed, 34 insertions(+), 1 deletion(-)
--
2 .31.1
next reply other threads:[~2022-10-17 22:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 22:33 Thomas Tai [this message]
2022-10-17 22:33 ` [PATCH V3 1/1] x86/sgx: Add code to inject hwpoison into SGX memory Thomas Tai
2022-10-18 2:21 ` HORIGUCHI NAOYA(堀口 直也)
2022-10-18 6:21 ` Miaohe Lin
2022-10-23 4:30 ` 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=20221017223305.578073-1-thomas.tai@oracle.com \
--to=thomas.tai@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@linux.intel.com \
--cc=jarkko@kernel.org \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=naoya.horiguchi@nec.com \
--cc=reinette.chatre@intel.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;
as well as URLs for NNTP newsgroup(s).