From: "Verma, Vishal L" <vishal.l.verma@intel.com>
To: "linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
"im, junhyeok" <junhyeok.im@samsung.com>
Cc: "Williams, Dan J" <dan.j.williams@intel.com>,
"bwidawsk@kernel.org" <bwidawsk@kernel.org>,
"Schofield, Alison" <alison.schofield@intel.com>
Subject: Re: [ndctl 0/3] Support for inject poison
Date: Mon, 8 May 2023 18:39:39 +0000 [thread overview]
Message-ID: <eb792ae37ebe68dee94d7445084ff99855f0268f.camel@intel.com> (raw)
In-Reply-To: <20230220045709.94027-1-junhyeok.im@samsung.com>
On Mon, 2023-02-20 at 13:57 +0900, Junhyeok Im wrote:
> This series adds new ability to inject poison, including library update
> and new command interface(inject-poison).
Hi Junhyeok,
With the now queued for the 6.4 kernel, the userspace side of this can
also target the next ndctl release, v78.
I see these patches will at least need a bit of rework to move from the
sysfs interface to the new debugfs interface.
Did you have a new revision of these in progress?
>
> Junhyeok Im (3):
> libcxl: add memdev inject poison support
> cxl: add inject-poison command to cxl tool
> Documentation: add man page documentation for inject-poison
>
> Documentation/cxl/cxl-inject-poison.txt | 42 ++++++++++++++++++++
> Documentation/cxl/lib/libcxl.txt | 4 ++
> Documentation/cxl/meson.build | 1 +
> cxl/builtin.h | 1 +
> cxl/cxl.c | 1 +
> cxl/lib/libcxl.c | 26 ++++++++++++
> cxl/lib/libcxl.sym | 5 +++
> cxl/libcxl.h | 1 +
> cxl/memdev.c | 53 +++++++++++++++++++++++--
> 9 files changed, 131 insertions(+), 3 deletions(-)
> create mode 100644 Documentation/cxl/cxl-inject-poison.txt
>
>
> base-commit: a88bdcfb4202c73aadfee6f83c5502eb5121cbd9
next prev parent reply other threads:[~2023-05-08 18:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230220045604epcas2p3bc0b1fb688c48ec0b8ae2512adba3513@epcas2p3.samsung.com>
2023-02-20 4:57 ` [ndctl 0/3] Support for inject poison Junhyeok Im
2023-02-20 4:57 ` [ndctl 1/3] libcxl: add memdev inject poison support Junhyeok Im
2023-02-27 2:43 ` Alison Schofield
2023-02-20 4:57 ` [ndctl 2/3] cxl: add inject-poison command to cxl tool Junhyeok Im
2023-02-27 3:21 ` Alison Schofield
2023-02-28 9:43 ` Junhyeok Im
2023-03-01 19:01 ` Verma, Vishal L
2023-02-27 3:25 ` Alison Schofield
2023-02-28 9:45 ` Junhyeok Im
2023-02-20 4:57 ` [ndctl 3/3] Documentation: add man page documentation for inject-poison Junhyeok Im
2023-02-27 2:38 ` [ndctl 0/3] Support for inject poison Alison Schofield
2023-02-28 9:31 ` Junhyeok Im
2023-05-08 18:39 ` Verma, Vishal L [this message]
2023-05-09 9:19 ` Junhyeok Im
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=eb792ae37ebe68dee94d7445084ff99855f0268f.camel@intel.com \
--to=vishal.l.verma@intel.com \
--cc=alison.schofield@intel.com \
--cc=bwidawsk@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=junhyeok.im@samsung.com \
--cc=linux-cxl@vger.kernel.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