From: alison.schofield@intel.com
To: Davidlohr Bueso <dave@stgolabs.net>,
Jonathan Cameron <jonathan.cameron@huawei.com>,
Dave Jiang <dave.jiang@intel.com>,
Alison Schofield <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Ira Weiny <ira.weiny@intel.com>,
Dan Williams <dan.j.williams@intel.com>
Cc: linux-cxl@vger.kernel.org
Subject: [PATCH 0/3] cxl: Support Poison Inject & Clear by HPA
Date: Mon, 23 Jun 2025 17:53:33 -0700 [thread overview]
Message-ID: <cover.1750725512.git.alison.schofield@intel.com> (raw)
From: Alison Schofield <alison.schofield@intel.com>
This series allows expert users to inject and clear poison by writing a
Host Physical Address (HPA) to a region debugfs files. At the core of this
new functionality is a helper that translates an HPA into a Device Physical
Address (DPA) and a memdev based on the region's decoder configuration.
The set is not merely a convenience wrapper for these region poison
operations as it enables these operations for XOR interleaved regions
where they were previously impossible.
Patch 1 adds a locked variant of the inject and clear poison ops to
support callers that must hold locks during the entire translation and
operation sequence.
Patch 2 introduces the translation logic capable of returning the memdev
and DPA for a given HPA.
Patch 3 exposes the capability through region debugfs attributes that
only appear when all participating memdevs support the poison commands.
These patches build on the existing memdev poison and region address
translation infrastructure and target debug and platform validation
scenarios.
Watch for the CXL Unit Test update to cxl-poison.sh posted separately
on this list.
Alison Schofield (3):
cxl/core: Add locked variants of the poison inject and clear funcs
cxl/region: Introduce HPA to DPA address translation
cxl/region: Add inject and clear poison by HPA
Documentation/ABI/testing/debugfs-cxl | 33 +++++
drivers/cxl/core/core.h | 4 +
drivers/cxl/core/memdev.c | 88 +++++++----
drivers/cxl/core/region.c | 201 ++++++++++++++++++++++++++
drivers/cxl/cxlmem.h | 2 +
5 files changed, 301 insertions(+), 27 deletions(-)
base-commit: 19272b37aa4f83ca52bdf9c16d5d81bdd1354494
--
2.37.3
next reply other threads:[~2025-06-24 0:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-24 0:53 alison.schofield [this message]
2025-06-24 0:53 ` [PATCH 1/3] cxl/core: Add locked variants of the poison inject and clear funcs alison.schofield
2025-06-24 13:38 ` Jonathan Cameron
2025-06-25 22:15 ` Dave Jiang
2025-06-30 19:37 ` Alison Schofield
2025-06-30 19:36 ` Alison Schofield
2025-06-24 0:53 ` [PATCH 2/3] cxl/region: Introduce HPA to DPA address translation alison.schofield
2025-06-24 14:27 ` Jonathan Cameron
2025-06-30 20:05 ` Alison Schofield
2025-07-01 20:40 ` Alison Schofield
2025-06-25 22:49 ` Dave Jiang
2025-06-30 20:12 ` Alison Schofield
2025-06-24 0:53 ` [PATCH 3/3] cxl/region: Add inject and clear poison by HPA alison.schofield
2025-06-24 8:06 ` kernel test robot
2025-06-24 14:33 ` Jonathan Cameron
2025-06-30 20:39 ` Alison Schofield
2025-06-25 23:05 ` dan.j.williams
2025-06-30 20:32 ` 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.1750725512.git.alison.schofield@intel.com \
--to=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=ira.weiny@intel.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.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 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.