Linux CXL
 help / color / mirror / Atom feed
From: Ben Cheatham <Benjamin.Cheatham@amd.com>
To: <nvdimm@lists.linux.dev>
Cc: <linux-cxl@vger.kernel.org>, <benjamin.cheatham@amd.com>,
	<alison.schofield@intel.com>
Subject: [ndctl PATCH 0/6] Add error injection support
Date: Thu, 24 Apr 2025 16:23:55 -0500	[thread overview]
Message-ID: <20250424212401.14789-1-Benjamin.Cheatham@amd.com> (raw)

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

Ben Cheatham (6):
  libcxl: Add debugfs path to CXL context
  libcxl: Add CXL protocol errors
  libcxl: Add poison injection functions
  cxl/list: Add debugfs option
  cxl/list: Add injectable-errors option
  cxl: Add inject-error command

 Documentation/cxl/cxl-inject-error.txt | 139 +++++++++++++++
 Documentation/cxl/cxl-list.txt         |  39 ++++-
 Documentation/cxl/meson.build          |   1 +
 cxl/builtin.h                          |   1 +
 cxl/cxl.c                              |   1 +
 cxl/filter.h                           |   3 +
 cxl/inject-error.c                     | 211 +++++++++++++++++++++++
 cxl/json.c                             |  30 ++++
 cxl/lib/libcxl.c                       | 225 +++++++++++++++++++++++++
 cxl/lib/libcxl.sym                     |  13 ++
 cxl/lib/private.h                      |  14 ++
 cxl/libcxl.h                           |  17 ++
 cxl/list.c                             |   9 +
 cxl/meson.build                        |   1 +
 util/json.h                            |   1 +
 15 files changed, 704 insertions(+), 1 deletion(-)
 create mode 100644 Documentation/cxl/cxl-inject-error.txt
 create mode 100644 cxl/inject-error.c

-- 
2.34.1


             reply	other threads:[~2025-04-24 21:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-24 21:23 Ben Cheatham [this message]
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

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=20250424212401.14789-1-Benjamin.Cheatham@amd.com \
    --to=benjamin.cheatham@amd.com \
    --cc=alison.schofield@intel.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