From: "Luck, Tony" <tony.luck@intel.com>
To: "Tai, Thomas" <thomas.tai@oracle.com>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"jarkko@kernel.org" <jarkko@kernel.org>,
"reinette.chatre@intel.co" <reinette.chatre@intel.co>,
"naoya.horiguchi@nec.com" <naoya.horiguchi@nec.com>,
"linmiaohe@huawei.com" <linmiaohe@huawei.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Tai, Thomas" <thomas.tai@oracle.com>
Subject: RE: [PATCH] x86/sgx: Add code to inject hwpoison into SGX memory
Date: Tue, 27 Sep 2022 20:34:44 +0000 [thread overview]
Message-ID: <SJ1PR11MB60836FCA1B8B317003CBF99FFC559@SJ1PR11MB6083.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220927183411.910077-1-thomas.tai@oracle.com>
> Inspired by commit c6acb1e7bf46 (x86/sgx: Add hook to error injection
> address validation), add a similar code in hwpoison_inject function to
> check if the address is located in SGX Memory. The error will then be
> handled by the arch_memory_failure function in the SGX driver.
Looks good to me.
[I wish that Linux hadn't called this "hwpoison_inject()" because there's nothing
hardware related about this injection. But you are just an innocent consumer of
that poor naming choice]
Reviewed-by: Tony Luck <tony.luck@intel.com>
-Tony
next prev parent reply other threads:[~2022-09-27 20:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 18:34 Thomas Tai
2022-09-27 20:34 ` Luck, Tony [this message]
2022-09-27 21:41 ` Thomas Tai
2022-09-28 7:59 ` Miaohe Lin
2022-09-28 12:23 ` Thomas Tai
2022-09-30 21:44 ` Jarkko Sakkinen
2022-10-02 14:56 ` Thomas Tai
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=SJ1PR11MB60836FCA1B8B317003CBF99FFC559@SJ1PR11MB6083.namprd11.prod.outlook.com \
--to=tony.luck@intel.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.co \
--cc=thomas.tai@oracle.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