public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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>,
	Dave Jiang <dave.jiang@intel.com>,
	Ben Widawsky <bwidawsk@kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>
Cc: Alison Schofield <alison.schofield@intel.com>,
	linux-cxl@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v7 0/6] CXL Poison List Retrieval & Tracing
Date: Fri, 17 Feb 2023 18:18:48 -0800	[thread overview]
Message-ID: <cover.1676685180.git.alison.schofield@intel.com> (raw)

From: Alison Schofield <alison.schofield@intel.com>

This is not targeting the 6.3 merge window.

Changes in v7:
- Update commit log wrt poison read for unmapped after mapped (Jonathan)
- Update comment wrt decoder modes and pmem/ram separation (Jonathan)
- Add dev_dbg() if mixed mode decoder appears
- Read poison on skip range first (Jonathan)
- trace: order fields (memdev, host, serial)
- trace: simplify host name get
- trace: use typical tabs
Link to v6: https://lore.kernel.org/linux-cxl/cover.1675983077.git.alison.schofield@intel.com/

Add support for retrieving device poison lists and store the returned
error records as kernel trace events.

The handling of the poison list is guided by the CXL 3.0 Specification
Section 8.2.9.8.4.1. [1] 

Example:
$ echo 1 > /sys/bus/cxl/devices/mem0/trigger_poison_list
cxl_poison: memdev=mem0 host=cxl_mem.0 serial=0 region=region4 region_uuid=117b2cf4-b160-4090-9361-ba31b9649317 hpa=0xf0d0000000 dpa=0x40000000 length=0x40 source=Internal flags= overflow_time=0

[1]: https://www.computeexpresslink.org/download-the-specification


Alison Schofield (6):
  cxl/mbox: Add GET_POISON_LIST mailbox command
  cxl/trace: Add TRACE support for CXL media-error records
  cxl/memdev: Add trigger_poison_list sysfs attribute
  cxl/region: Provide region info to the cxl_poison trace event
  cxl/trace: Add an HPA to cxl_poison trace events
  tools/testing/cxl: Mock support for Get Poison List

 Documentation/ABI/testing/sysfs-bus-cxl | 14 ++++
 drivers/cxl/core/core.h                 |  5 ++
 drivers/cxl/core/mbox.c                 | 74 +++++++++++++++++++
 drivers/cxl/core/memdev.c               | 68 ++++++++++++++++++
 drivers/cxl/core/region.c               | 89 +++++++++++++++++++++++
 drivers/cxl/core/trace.c                | 94 +++++++++++++++++++++++++
 drivers/cxl/core/trace.h                | 91 ++++++++++++++++++++++++
 drivers/cxl/cxlmem.h                    | 69 +++++++++++++++++-
 drivers/cxl/pci.c                       |  4 ++
 tools/testing/cxl/test/mem.c            | 42 +++++++++++
 10 files changed, 549 insertions(+), 1 deletion(-)


base-commit: a5fcd228ca1db9810ba1ed461c90b6ee933b9daf
-- 
2.37.3


             reply	other threads:[~2023-02-18  2:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-18  2:18 alison.schofield [this message]
2023-02-18  2:18 ` [PATCH v7 1/6] cxl/mbox: Add GET_POISON_LIST mailbox command alison.schofield
2023-02-18  2:18 ` [PATCH v7 2/6] cxl/trace: Add TRACE support for CXL media-error records alison.schofield
2023-02-18  2:18 ` [PATCH v7 3/6] cxl/memdev: Add trigger_poison_list sysfs attribute alison.schofield
2023-03-03 15:42   ` Jonathan Cameron
2023-03-04  5:29     ` Alison Schofield
2023-02-18  2:18 ` [PATCH v7 4/6] cxl/region: Provide region info to the cxl_poison trace event alison.schofield
2023-03-03 16:46   ` Jonathan Cameron
2023-03-03 17:35     ` Alison Schofield
2023-03-04  5:51       ` Alison Schofield
2023-02-18  2:18 ` [PATCH v7 5/6] cxl/trace: Add an HPA to cxl_poison trace events alison.schofield
2023-02-18  2:18 ` [PATCH v7 6/6] tools/testing/cxl: Mock support for Get Poison List 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.1676685180.git.alison.schofield@intel.com \
    --to=alison.schofield@intel.com \
    --cc=bwidawsk@kernel.org \
    --cc=dan.j.williams@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=ira.weiny@intel.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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