From: alison.schofield@intel.com
To: Vishal Verma <vishal.l.verma@intel.com>
Cc: Alison Schofield <alison.schofield@intel.com>,
nvdimm@lists.linux.dev, linux-cxl@vger.kernel.org
Subject: [ndctl PATCH v8 0/7] Support poison list retrieval
Date: Thu, 22 Feb 2024 18:15:37 -0800 [thread overview]
Message-ID: <cover.1708653303.git.alison.schofield@intel.com> (raw)
From: Alison Schofield <alison.schofield@intel.com>
Changes since v7:
- Replace spaces w tab in cxl-poison.sh unit test (Vishal)
- Rebase to latest ndctl/pending branch
Link to v7: https://lore.kernel.org/nvdimm/cover.1707351560.git.alison.schofield@intel.com/
Add the option to add a memory devices poison list to the cxl-list
json output. Offer the option by memdev and by region. Sample usage:
# cxl list -m mem1 --media-errors
[
{
"memdev":"mem1",
"pmem_size":1073741824,
"ram_size":1073741824,
"serial":1,
"numa_node":1,
"host":"cxl_mem.1",
"media_errors":[
{
"dpa":0,
"length":64,
"source":"Internal"
},
{
"decoder":"decoder10.0",
"hpa":1035355557888,
"dpa":1073741824,
"length":64,
"source":"External"
},
{
"decoder":"decoder10.0",
"hpa":1035355566080,
"dpa":1073745920,
"length":64,
"source":"Injected"
}
]
}
]
# cxl list -r region5 --media-errors
[
{
"region":"region5",
"resource":1035355553792,
"size":2147483648,
"type":"pmem",
"interleave_ways":2,
"interleave_granularity":4096,
"decode_state":"commit",
"media_errors":[
{
"decoder":"decoder10.0",
"hpa":1035355557888,
"dpa":1073741824,
"length":64,
"source":"External"
},
{
"decoder":"decoder8.1",
"hpa":1035355566080,
"dpa":1073745920,
"length":64,
"source":"Internal"
}
]
}
]
Alison Schofield (7):
libcxl: add interfaces for GET_POISON_LIST mailbox commands
cxl: add an optional pid check to event parsing
cxl/event_trace: add a private context for private parsers
cxl/event_trace: add helpers get_field_[string|data]()
cxl/list: collect and parse media_error records
cxl/list: add --media-errors option to cxl list
cxl/test: add cxl-poison.sh unit test
Documentation/cxl/cxl-list.txt | 79 +++++++++-
cxl/event_trace.c | 53 ++++++-
cxl/event_trace.h | 9 +-
cxl/filter.h | 3 +
cxl/json.c | 261 +++++++++++++++++++++++++++++++++
cxl/lib/libcxl.c | 47 ++++++
cxl/lib/libcxl.sym | 2 +
cxl/libcxl.h | 2 +
cxl/list.c | 3 +
test/cxl-poison.sh | 137 +++++++++++++++++
test/meson.build | 2 +
11 files changed, 594 insertions(+), 4 deletions(-)
create mode 100644 test/cxl-poison.sh
base-commit: 4d767c0c9b91d254e8ff0d7f0d3be04a498ad9f0
--
2.37.3
next reply other threads:[~2024-02-23 2:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 2:15 alison.schofield [this message]
2024-02-23 2:15 ` [ndctl PATCH v8 1/7] libcxl: add interfaces for GET_POISON_LIST mailbox commands alison.schofield
2024-02-23 2:15 ` [ndctl PATCH v8 2/7] cxl: add an optional pid check to event parsing alison.schofield
2024-02-23 2:15 ` [ndctl PATCH v8 3/7] cxl/event_trace: add a private context for private parsers alison.schofield
2024-02-23 2:15 ` [ndctl PATCH v8 4/7] cxl/event_trace: add helpers get_field_[string|data]() alison.schofield
2024-02-23 2:15 ` [ndctl PATCH v8 5/7] cxl/list: collect and parse media_error records alison.schofield
2024-02-23 2:15 ` [ndctl PATCH v8 6/7] cxl/list: add --media-errors option to cxl list alison.schofield
2024-02-23 2:15 ` [ndctl PATCH v8 7/7] cxl/test: add cxl-poison.sh unit test 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=cover.1708653303.git.alison.schofield@intel.com \
--to=alison.schofield@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.