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 v2 0/2] Return EBUSY on inject poison limit reached
Date: Sat, 6 Jul 2024 18:53:42 -0700 [thread overview]
Message-ID: <cover.1720316188.git.alison.schofield@intel.com> (raw)
From: Alison Schofield <alison.schofield@intel.com>
Changes in v2:
- Use poison_inject_dev_max in cxl-test dev_dbg() msg and note that
change in the Patch 2 commit log (Xingtao)
Link to v1: https://lore.kernel.org/cover.1720052137.git.alison.schofield@intel.com/
Validation users are asking for the ability to recognize when
their injection testing has hit the limit of the device.
Change the drivers error code for this failure to EBUSY and do
the same in the cxl-test mock of inject poison.
Alison Schofield (2):
cxl/memdev: Replace ENXIO with EBUSY for inject poison limit reached
cxl/test: Replace ENXIO with EBUSY for inject poison limit reached
Documentation/ABI/testing/debugfs-cxl | 7 ++++---
drivers/cxl/cxlmem.h | 2 +-
tools/testing/cxl/test/mem.c | 15 +++++++--------
3 files changed, 12 insertions(+), 12 deletions(-)
base-commit: 22a40d14b572deb80c0648557f4bd502d7e83826
--
2.37.3
next reply other threads:[~2024-07-07 1:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-07 1:53 alison.schofield [this message]
2024-07-07 1:53 ` [PATCH v2 1/2] cxl/memdev: Replace ENXIO with EBUSY for inject poison limit reached alison.schofield
2024-07-07 1:53 ` [PATCH v2 2/2] cxl/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.1720316188.git.alison.schofield@intel.com \
--to=alison.schofield@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=ira.weiny@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox