From: alison.schofield@intel.com
To: Dan Williams <dan.j.williams@intel.com>,
Ira Weiny <ira.weiny@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Ben Widawsky <bwidawsk@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>
Cc: Alison Schofield <alison.schofield@intel.com>,
linux-cxl@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] CXL Poison List Retrieval & Tracing
Date: Tue, 14 Jun 2022 17:10:25 -0700 [thread overview]
Message-ID: <cover.1655250669.git.alison.schofield@intel.com> (raw)
From: Alison Schofield <alison.schofield@intel.com>
Introducing the first piece of support for CXL Media Errors,
offering the ability to retrieve a devices poison list and
store the returned error records as kernel trace events.
The handling of the poison list is guided by the CXL 2.0 Spec
Section 8.2.9.5.4.1. [1] The usage of Trace Events to store the
Media Error records is a first look at the proposed handling
of CXL ARS events.
Example command line usage:
$ trace-cmd record -e cxl_poison_list
$ echo 1 > /sys/bus/cxl/devices/mem1/get_poison
$ trace-cmd report trace.dat
cxl_poison_list: memdev: mem3 source EXTERNAL start 0x41 length 0x2
cxl_poison_list: memdev: mem3 source INTERNAL start 0xc2 length 0x3
cxl_poison_list: memdev: mem3 source INJECTED start 0x183 length 0x4
cxl_poison_list: memdev: mem3 source INVALID start 0x284 length 0x5
cxl_poison_list: memdev: mem3 source VENDOR start 0x707 length 0x8
[1]: https://www.computeexpresslink.org/download-the-specification
Alison Schofield (3):
trace, cxl: Introduce a TRACE_EVENT for CXL Poison Records
cxl/mbox: Add GET_POISON_LIST mailbox command support
cxl/core: Add sysfs attribute get_poison for list retrieval
Documentation/ABI/testing/sysfs-bus-cxl | 13 +++++
drivers/cxl/cxlmem.h | 43 ++++++++++++++
include/trace/events/cxl.h | 60 ++++++++++++++++++++
drivers/cxl/core/mbox.c | 75 +++++++++++++++++++++++++
drivers/cxl/core/memdev.c | 32 +++++++++++
5 files changed, 223 insertions(+)
create mode 100644 include/trace/events/cxl.h
base-commit: 2263e9ed65887cc7c6e977f372596199d2c9f4af
--
2.31.1
next reply other threads:[~2022-06-15 0:11 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 0:10 alison.schofield [this message]
2022-06-15 0:10 ` [PATCH 1/3] trace, cxl: Introduce a TRACE_EVENT for CXL Poison Records alison.schofield
2022-06-15 1:15 ` Steven Rostedt
2022-06-16 19:45 ` Davidlohr Bueso
2022-06-17 16:17 ` Jonathan Cameron
2022-06-17 18:04 ` Dan Williams
2022-06-15 0:10 ` [PATCH 2/3] cxl/mbox: Add GET_POISON_LIST mailbox command support alison.schofield
2022-06-15 3:22 ` Ira Weiny
2022-06-15 5:07 ` Alison Schofield
2022-06-15 15:01 ` Ira Weiny
2022-06-15 17:19 ` Alison Schofield
2022-06-16 19:43 ` Davidlohr Bueso
2022-06-16 20:34 ` Alison Schofield
2022-06-16 21:47 ` Davidlohr Bueso
2022-06-16 22:10 ` Alison Schofield
2022-06-16 22:20 ` Davidlohr Bueso
2022-06-16 22:45 ` Davidlohr Bueso
2022-06-16 23:15 ` Alison Schofield
2022-06-16 23:44 ` Verma, Vishal L
2022-06-17 0:03 ` Davidlohr Bueso
2022-06-17 19:02 ` Dan Williams
2022-06-20 10:53 ` Jonathan Cameron
2022-06-17 13:01 ` Jonathan Cameron
2022-06-17 14:05 ` Jonathan Cameron
2022-06-17 16:29 ` Alison Schofield
2022-06-17 17:29 ` Davidlohr Bueso
2022-06-17 19:32 ` Dan Williams
2022-06-20 10:56 ` Jonathan Cameron
2022-06-17 19:27 ` Dan Williams
2022-06-20 11:30 ` Jonathan Cameron
2022-06-17 18:26 ` Dan Williams
2022-06-15 0:10 ` [PATCH 3/3] cxl/core: Add sysfs attribute get_poison for list retrieval alison.schofield
2022-06-15 3:30 ` Ira Weiny
2022-06-16 15:04 ` Jonathan Cameron
2022-06-16 20:39 ` Alison Schofield
2022-06-17 18:42 ` Dan Williams
2022-06-18 0:21 ` Alison Schofield
2022-06-18 1:08 ` Dan Williams
2022-06-18 1:35 ` Alison Schofield
2022-06-17 17:52 ` [PATCH 0/3] CXL Poison List Retrieval & Tracing 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=cover.1655250669.git.alison.schofield@intel.com \
--to=alison.schofield@intel.com \
--cc=bwidawsk@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox