public inbox for nvdimm@lists.linux.dev
 help / color / mirror / Atom feed
From: Dave Jiang <dave.jiang@intel.com>
To: linux-cxl@vger.kernel.org, nvdimm@lists.linux.dev
Cc: dave@stgolabs.net, jonathan.cameron@huawei.com,
	alison.schofield@intel.com, vishal.l.verma@intel.com,
	ira.weiny@intel.com, dan.j.williams@intel.com
Subject: [NDCTL PATCH v2 0/2] cxl: Add tests for extended linear cache support
Date: Thu, 20 Nov 2025 17:20:16 -0700	[thread overview]
Message-ID: <20251121002018.4136006-1-dave.jiang@intel.com> (raw)

v2:
- skip if no extended_linear_cache mod param. (Alison)
- Cleanup at the end. (Alison)
- Fix shellcheck double quote issues. (Alison)
- Err if elc region not found for cxl_test. (Alison)
- Add missing call to find_region() (Alison)
- Fixup jq query when setup also has qemu cxl devices.
- Dropped folded in patches. 2 and 3.
- Move poison changes to cxl-poison.sh and drop 4 and 5.

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 augments the test to go through the poison handling flow
via the poison injection testing.

Dave Jiang (2):
  cxl/test: Add test for extended linear cache support
  cxl/test: Add support for poison test for ELC

 test/cxl-elc.sh    | 95 ++++++++++++++++++++++++++++++++++++++++++++++
 test/cxl-poison.sh | 61 ++++++++++++++++++-----------
 test/meson.build   |  2 +
 3 files changed, 136 insertions(+), 22 deletions(-)
 create mode 100755 test/cxl-elc.sh


base-commit: 8a94356bc9c0af493be76c0428eee24fe2f5594a
-- 
2.51.1


             reply	other threads:[~2025-11-21  0:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-21  0:20 Dave Jiang [this message]
2025-11-21  0:20 ` [NDCTL PATCH v2 1/2] cxl/test: Add test for extended linear cache support Dave Jiang
2025-12-02 22:15   ` Alison Schofield
2025-12-02 22:22     ` Alison Schofield
2025-11-21  0:20 ` [NDCTL PATCH v2 2/2] cxl/test: Add support for poison test for ELC Dave Jiang
2025-12-02 22:21   ` 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=20251121002018.4136006-1-dave.jiang@intel.com \
    --to=dave.jiang@intel.com \
    --cc=alison.schofield@intel.com \
    --cc=dan.j.williams@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