From: "Luck, Tony" <tony.luck@intel.com>
To: Shiyang Ruan <ruansy.fnst@fujitsu.com>,
Jonathan Cameron <Jonathan.Cameron@Huawei.com>,
"Williams, Dan J" <dan.j.williams@intel.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
"dave@stgolabs.net" <dave@stgolabs.net>,
"Weiny, Ira" <ira.weiny@intel.com>,
"Schofield, Alison" <alison.schofield@intel.com>,
"Jiang, Dave" <dave.jiang@intel.com>,
"Verma, Vishal L" <vishal.l.verma@intel.com>,
Borislav Petkov <bp@alien8.de>,
"James Morse" <james.morse@arm.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Robert Richter <rric@kernel.org>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
Miaohe Lin <linmiaohe@huawei.com>,
"Naoya Horiguchi" <nao.horiguchi@gmail.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: RE: [RFC PATCH] cxl: avoid duplicating report from MCE & device
Date: Wed, 26 Jun 2024 15:56:29 +0000 [thread overview]
Message-ID: <SJ1PR11MB6083829FC72B2230C1CB1599FCD62@SJ1PR11MB6083.namprd11.prod.outlook.com> (raw)
In-Reply-To: <bc58d99a-785f-4bb3-a9c9-9cf50ea7e06d@fujitsu.com>
>> So recovery has some risk, but very little upside benefit.
>
> Since the hardware provides the instruction(CPU)/command(CXL) to clear
> the poison, we could make the function work, at least as an optional
> feature. Then users could decide to use it or not after evaluating the
> risk and benefit.
>
> I think doing recovery is an improvement step, and may need a lot of
> discussion. I'm not sure if we could reach a conclusion in this thread.
> Just hope more comments on the original problem (duplicate report) to
> solve in this patch.
Post a patch to implement poison clearing/recovery with some way to opt-in
to get the discussion started. If it doesn't add too much complexity perhaps
it will be accepted.
-Tony
next prev parent reply other threads:[~2024-06-26 15:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240618165310.877974-1-ruansy.fnst@fujitsu.com>
2024-06-20 17:02 ` Jonathan Cameron
2024-06-21 10:16 ` Shiyang Ruan
2024-06-21 17:21 ` Jonathan Cameron
2024-06-21 17:59 ` Dan Williams
2024-06-21 18:45 ` Jonathan Cameron
2024-06-21 20:44 ` Luck, Tony
2024-06-26 6:03 ` Shiyang Ruan
2024-06-26 15:56 ` Luck, Tony [this message]
2024-07-19 6:24 ` Shiyang Ruan
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=SJ1PR11MB6083829FC72B2230C1CB1599FCD62@SJ1PR11MB6083.namprd11.prod.outlook.com \
--to=tony.luck@intel.com \
--cc=Jonathan.Cameron@Huawei.com \
--cc=alison.schofield@intel.com \
--cc=bp@alien8.de \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=ira.weiny@intel.com \
--cc=james.morse@arm.com \
--cc=linmiaohe@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mchehab@kernel.org \
--cc=nao.horiguchi@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=rric@kernel.org \
--cc=ruansy.fnst@fujitsu.com \
--cc=vishal.l.verma@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