From: Dan Williams <dan.j.williams@intel.com>
To: Alison Schofield <alison.schofield@intel.com>,
<nvdimm@lists.linux.dev>, <linux-cxl@vger.kernel.org>
Cc: Dan Williams <dan.j.williams@intel.com>,
Alison Schofield <alison.schofield@intel.com>
Subject: Re: [ndctl PATCH] test/cxl-dax-hmem.sh: validate dax_hmem vs CXL collisions
Date: Wed, 1 Apr 2026 15:36:30 -0700 [thread overview]
Message-ID: <69cd9deedca87_1b0cc610036@dwillia2-mobl4.notmuch> (raw)
In-Reply-To: <20260401221336.2894052-1-alison.schofield@intel.com>
Alison Schofield wrote:
> From: Dan Williams <dan.j.williams@intel.com>
>
> Use the new "cxl_test.hmem_test" and "cxl_test.fail_autoassemble"
> module options to implement a new cxl-dax-hmem.sh test. The test
> checks dax_hmem takeover of Soft Reserve ranges that collide with
> autoassembled CXL regions. It depends on the cxl_mock_mem driver
> to launch multiple async probes before the dax_hmem driver attaches.
>
> [as: do_skip on missing params, explicit param usage, robust unload,
> check_dmesg, misc style]
Thanks! Looks good.
prev parent reply other threads:[~2026-04-01 22:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-01 22:13 [ndctl PATCH] test/cxl-dax-hmem.sh: validate dax_hmem vs CXL collisions Alison Schofield
2026-04-01 22:36 ` Dan Williams [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=69cd9deedca87_1b0cc610036@dwillia2-mobl4.notmuch \
--to=dan.j.williams@intel.com \
--cc=alison.schofield@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
/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