From: Alison Schofield <alison.schofield@intel.com>
To: Dave Jiang <dave.jiang@intel.com>
Cc: <linux-cxl@vger.kernel.org>, <nvdimm@lists.linux.dev>,
<dave@stgolabs.net>, <jonathan.cameron@huawei.com>,
<vishal.l.verma@intel.com>, <ira.weiny@intel.com>,
<dan.j.williams@intel.com>
Subject: Re: [NDCTL PATCH 0/5] cxl: Add tests for extended linear cache support
Date: Fri, 14 Nov 2025 17:20:26 -0800 [thread overview]
Message-ID: <aRfVWuVMb3LDr7S3@aschofie-mobl2.lan> (raw)
In-Reply-To: <20251031174003.3547740-1-dave.jiang@intel.com>
On Fri, Oct 31, 2025 at 10:39:58AM -0700, Dave Jiang wrote:
> The series adds unit tests to verify the kernel support for extended
> linear cache (ELC). Added a test to check if the ELC region is setup
> correctly, and another test to go through the poison handling flow
> via the poison injection testing.
>
>
> Dave Jiang (5):
> cxl/test: Add test for extended linear cache support
> cxl/test: Fix cxl-poison.sh to detect the correct elc sysfs attrib
> cxl/test: Move cxl-poison.sh to use cxl_test auto region
The next 2 patches may add more complexity than is needed by splitting
the work among a common file and 2 test scripts. Consider keeping the
work in one file and wrapping the test execution in a 'run_poison_tests'
function. Then call it that after each load of the module, like -
run_poison_tests
.
.
.
modprobe -r cxl_test
modprobe cxl_test
run_poison_tests
modprobe -r cxl_test
modprobe cxl_test extended_linear_cache=1
run_poison_tests
modprobe -r cxl_test
> cxl/test: Move common part of poison unit test to common file
> cxl/test: Add support for poison test for ELC
>
> test/common-poison | 202 ++++++++++++++++++++++++++++++++++++++++
> test/cxl-elc.sh | 89 ++++++++++++++++++
> test/cxl-poison-elc.sh | 41 +++++++++
> test/cxl-poison.sh | 203 +----------------------------------------
> test/meson.build | 4 +
> 5 files changed, 338 insertions(+), 201 deletions(-)
> create mode 100644 test/common-poison
> create mode 100755 test/cxl-elc.sh
> create mode 100755 test/cxl-poison-elc.sh
>
>
> base-commit: 01c90830d65b6b331986f5996dcf6ad73c1579f4
> --
> 2.51.0
>
prev parent reply other threads:[~2025-11-15 1:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-31 17:39 [NDCTL PATCH 0/5] cxl: Add tests for extended linear cache support Dave Jiang
2025-10-31 17:39 ` [NDCTL PATCH 1/5] cxl/test: Add test " Dave Jiang
2025-11-15 1:00 ` Alison Schofield
2025-11-15 2:54 ` Alison Schofield
2025-11-16 1:49 ` Alison Schofield
2025-10-31 17:40 ` [NDCTL PATCH 2/5] cxl/test: Fix cxl-poison.sh to detect the correct elc sysfs attrib Dave Jiang
2025-11-15 0:54 ` Alison Schofield
2025-10-31 17:40 ` [NDCTL PATCH 3/5] cxl/test: Move cxl-poison.sh to use cxl_test auto region Dave Jiang
2025-11-15 1:07 ` Alison Schofield
2025-10-31 17:40 ` [NDCTL PATCH 4/5] cxl/test: Move common part of poison unit test to common file Dave Jiang
2025-10-31 17:40 ` [NDCTL PATCH 5/5] cxl/test: Add support for poison test for ELC Dave Jiang
2025-11-15 1:20 ` Alison Schofield [this message]
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=aRfVWuVMb3LDr7S3@aschofie-mobl2.lan \
--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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox