From: Alison Schofield <alison.schofield@intel.com>
To: Richard Cheng <icheng@nvidia.com>
Cc: <dave@stgolabs.net>, <jic23@kernel.org>, <dave.jiang@intel.com>,
<vishal.l.verma@intel.com>, <iweiny@kernel.org>,
<ming.li@zohomail.com>, <kobak@nvidia.com>, <kaihengf@nvidia.com>,
<linux-cxl@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<nvdimm@lists.linux.dev>
Subject: Re: [ndctl PATCH] test/cxl-topology.sh: test zero-sized decoders
Date: Thu, 30 Jul 2026 18:36:42 -0700 [thread overview]
Message-ID: <amv8KubdJk0PC9SQ@aschofie-mobl2.lan> (raw)
In-Reply-To: <20260709022857.18732-1-icheng@nvidia.com>
On Thu, Jul 09, 2026 at 10:28:57AM +0800, Richard Cheng wrote:
> The kernel series [1] teaches the CXL core to enumerate committed
> zero-sized HDM decoders and adds the opt-in mock_zero_size_decoders
> cxl_test topology. Since the param defaults off, the existing ndctl
> suite never exercises that path, leaving the series without userspace
> regression coverage.
>
> After the existing default-topology checks, detect the module param with
> modinfo. When available, reload cxl_test with mock_zero_size_decoders=1,
> discover both endpoint decoders through the auto-region mapping, and
> verify that decoder IDs 1 and 2 exist with size 0 and locked set.
> Unsupported kernels retain the existing baseline coverage.
>
> Tested on arm64. The focused test passed. The full CXL suite passed and 1
> unrelated cxl-security skip. Four zero-sized endpoint decoders were
> validated, cxl_test unloaded cleanly, and no relevant dmesg errors were
> shown.
>
> [1]:
> https://lore.kernel.org/linux-cxl/20260708104024.68029-1-icheng@nvidia.com/
> Signed-off-by: Richard Cheng <icheng@nvidia.com>
Applied w some minor edits:
[as: move new work to a function and add code comments]
https://github.com/pmem/ndctl/commit/02754b5c4b60
Richard - This got me thinking about how we display these with
'cxl list'. Please take a look at my follow patches.
prev parent reply other threads:[~2026-07-31 1:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 2:28 Richard Cheng
2026-07-31 1:36 ` 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=amv8KubdJk0PC9SQ@aschofie-mobl2.lan \
--to=alison.schofield@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=icheng@nvidia.com \
--cc=iweiny@kernel.org \
--cc=jic23@kernel.org \
--cc=kaihengf@nvidia.com \
--cc=kobak@nvidia.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.li@zohomail.com \
--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
all inboxes | Powered by JetHome®