From: Shiyang Ruan <ruansy.fnst@fujitsu.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Jonathan.Cameron@huawei.com, dave@stgolabs.net,
ira.weiny@intel.com, qemu-devel@nongnu.org,
linux-cxl@vger.kernel.org
Subject: Re: [RFC PATCH v2 4/6] cxl/core: report poison when injecting from debugfs
Date: Wed, 3 Apr 2024 23:07:25 +0800 [thread overview]
Message-ID: <ae5c692f-695a-460b-91e2-6f06fd7f7a05@fujitsu.com> (raw)
In-Reply-To: <6607704e65437_19e0294e1@dwillia2-mobl3.amr.corp.intel.com.notmuch>
在 2024/3/30 9:52, Dan Williams 写道:
> Shiyang Ruan wrote:
>> Poison injection from debugfs is silent too. Add calling
>> cxl_mem_report_poison() to make it able to do memory_failure().
>
> Why does this needs to be signalled? It is a debug interface, the
> debugger can also trigger a read after the injection, or trigger page
> soft-offline.
I was thinking that the poison injection should trigger a chain of
events. So, for debugfs they should be independent, right? I wasn't
aware of this. Will drop this patch.
--
Thanks,
Ruan.
next prev parent reply other threads:[~2024-04-03 15:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-29 6:36 [RFC PATCH v2 0/6] cxl: add poison event handler Shiyang Ruan
2024-03-29 6:36 ` [RFC PATCH v2 1/6] cxl/core: correct length of DPA field masks Shiyang Ruan
2024-03-30 1:37 ` Dan Williams
2024-04-01 9:14 ` Shiyang Ruan
2024-03-29 6:36 ` [RFC PATCH v2 2/6] cxl/core: introduce cxl_mem_report_poison() Shiyang Ruan
2024-03-30 1:39 ` Dan Williams
2024-03-29 6:36 ` [RFC PATCH v2 3/6] cxl/core: add report option for cxl_mem_get_poison() Shiyang Ruan
2024-03-30 1:50 ` Dan Williams
2024-04-03 14:56 ` Shiyang Ruan
2024-04-04 13:46 ` Jonathan Cameron
2024-03-29 6:36 ` [RFC PATCH v2 4/6] cxl/core: report poison when injecting from debugfs Shiyang Ruan
2024-03-29 18:13 ` Alison Schofield
2024-03-30 1:52 ` Dan Williams
2024-04-03 15:07 ` Shiyang Ruan [this message]
2024-03-29 6:36 ` [RFC PATCH v2 5/6] cxl: add definition for transaction types Shiyang Ruan
2024-03-30 1:53 ` Dan Williams
2024-03-29 6:36 ` [RFC PATCH v2 6/6] cxl/core: add poison injection event handler Shiyang Ruan
2024-03-29 18:27 ` Alison Schofield
2024-03-29 17:43 ` [RFC PATCH v2 0/6] cxl: add poison " Alison Schofield
2024-03-29 18:22 ` Dan Williams
2024-03-29 19:38 ` Alison Schofield
2024-03-29 20:56 ` Dan Williams
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=ae5c692f-695a-460b-91e2-6f06fd7f7a05@fujitsu.com \
--to=ruansy.fnst@fujitsu.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=dan.j.williams@intel.com \
--cc=dave@stgolabs.net \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
/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