Linux CXL
 help / color / mirror / Atom feed
From: Alison Schofield <alison.schofield@intel.com>
To: Ben Cheatham <benjamin.cheatham@amd.com>
Cc: Junhyeok Im <junhyeok.im@samsung.com>, <nvdimm@lists.linux.dev>,
	<linux-cxl@vger.kernel.org>
Subject: Re: [ndctl PATCH 0/6] Add error injection support
Date: Tue, 29 Apr 2025 17:53:08 -0700	[thread overview]
Message-ID: <aBF0dA2NzjrfWVBJ@aschofie-mobl2.lan> (raw)
In-Reply-To: <2bfda6ab-7eb7-4166-832f-06a6a3216d0e@amd.com>

On Tue, Apr 29, 2025 at 03:01:42PM -0500, Ben Cheatham wrote:
> 
> On 4/28/25 9:35 PM, Alison Schofield wrote:
> > On Thu, Apr 24, 2025 at 04:23:55PM -0500, Ben Cheatham wrote:
> >> This series adds support for injecting CXL protocol (CXL.cache/mem)
> >> errors[1] into CXL RCH Downstream ports and VH root ports[2] and
> >> poison into CXL memory devices through the CXL debugfs. Errors are
> >> injected using a new 'inject-error' command, while errors are reported
> >> using a new cxl-list "-N"/"--injectable-errors" option.
> >>
> >> The 'inject-error' command and "-N" option of cxl-list both require
> >> access to the CXL driver's debugfs. Because the debugfs doesn't have a
> >> required mount point, a "--debugfs" option is added to both cxl-list and
> >> cxl-inject-error to specify the path to the debugfs if it isn't mounted
> >> to the usual place (/sys/kernel/debug).
> >>
> >> The documentation for the new cxl-inject-error command shows both usage
> >> and the possible device/error types, as well as how to retrieve them
> >> using cxl-list. The documentation for cxl-list has also been updated to
> >> show the usage of the new injectable errors and debugfs options.
> >>
> >> [1]: ACPI v6.5 spec, section 18.6.4
> >> [2]: ACPI v6.5 spec, table 18.31
> > 
> > Hi Ben,
> > 
> > Junkyeok Im posted a set for inject & clear poison back in 2023.[1] It
> > went through one round of review but was a bit ahead of it's time as we
> > were still working out the presentation of media-errors in the trigger
> > poison patch set. I'll 'cc them here in case they have interest and can
> > help review thi set.
> 
> Thanks for pointing this out. I forgot to look for an existing set before
> implementing it myself, sorry about that :/.
> 
> I'd be willing to drop the poison support from this set and use Junhyeok's
> instead, integrate it into this one, or leave it as-is.

I should have recalled at the RFC time. Anyway, compare and contrast and
select the best path forward.

> 
> > 
> > How come you're not interested in implementing clear-poison?
> 
> It is implemented, it's a flag ("--clear") for the inject-error command. I forgot
> to mention it in the cover letter, I can add it in v2.

Ah, I haven't reviewed yet to see that. I'm going to ask for that to be
its own command. We may get into some naming brouhaha. You are using the
word 'error' for multiple types of errors and we used 'media-error' specifically
for device poison. I'll put more thought into it when I review in detail.

> 
> Thanks,
> Ben

      reply	other threads:[~2025-04-30  0:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-24 21:23 [ndctl PATCH 0/6] Add error injection support Ben Cheatham
2025-04-24 21:23 ` [PATCH 1/6] libcxl: Add debugfs path to CXL context Ben Cheatham
2025-04-24 21:23 ` [PATCH 2/6] libcxl: Add CXL protocol errors Ben Cheatham
2025-04-24 21:23 ` [PATCH 3/6] libcxl: Add poison injection functions Ben Cheatham
2025-04-24 21:23 ` [PATCH 4/6] cxl/list: Add debugfs option Ben Cheatham
2025-04-24 21:24 ` [PATCH 5/6] cxl/list: Add injectable-errors option Ben Cheatham
2025-04-24 21:24 ` [PATCH 6/6] cxl: Add inject-error command Ben Cheatham
2025-04-29  2:35 ` [ndctl PATCH 0/6] Add error injection support Alison Schofield
2025-04-29 20:01   ` Ben Cheatham
2025-04-30  0:53     ` Alison Schofield [this message]

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=aBF0dA2NzjrfWVBJ@aschofie-mobl2.lan \
    --to=alison.schofield@intel.com \
    --cc=benjamin.cheatham@amd.com \
    --cc=junhyeok.im@samsung.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=nvdimm@lists.linux.dev \
    /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