From: Richard Cheng <icheng@nvidia.com>
To: Alison Schofield <alison.schofield@intel.com>
Cc: jic23@kernel.org, dave@stgolabs.net, dave.jiang@intel.com,
vishal.l.verma@intel.com, djbw@kernel.org,
danwilliams@nvidia.com, iweiny@kernel.org, ming.li@zohomail.com,
linux-cxl@vger.kernel.org, linux-kernel@vger.kernel.org,
newtonl@nvidia.com, kristinc@nvidia.com, kaihengf@nvidia.com,
kobak@nvidia.com, vaslot@nvidia.com, mochs@nvidia.com
Subject: Re: [PATCH v8 0/3] Support zero-sized HDM decoders
Date: Wed, 5 Aug 2026 11:16:39 +0800 [thread overview]
Message-ID: <anKpY6Y1Sqne1f7Y@MWDK4CY14F> (raw)
In-Reply-To: <amzu-kZU36ivFhZ0@aschofie-mobl2.lan>
On Fri, Jul 31, 2026 at 11:52:42AM +0800, Alison Schofield wrote:
> On Fri, Jul 31, 2026 at 02:48:59PM +0800, Richard Cheng wrote:
>
> skip...
>
> >
> > Full cxl suite with mock_zero_size_decoders off -- no failures:
> > """
> > $ sudo env "PATH=$PATH" meson test -C build --suite cxl \
> > --num-processes 1 -t 6 --print-errorlogs
> > 1/16 ndctl:cxl / cxl-topology.sh OK 7.81s
> > 2/16 ndctl:cxl / cxl-region-sysfs.sh OK 5.28s
> > 3/16 ndctl:cxl / cxl-labels.sh OK 3.27s
> > 4/16 ndctl:cxl / cxl-create-region.sh OK 10.70s
> > 5/16 ndctl:cxl / cxl-xor-region.sh OK 5.76s
> > 6/16 ndctl:cxl / cxl-events.sh OK 2.77s
> > 7/16 ndctl:cxl / cxl-sanitize.sh OK 5.73s
> > 8/16 ndctl:cxl / cxl-destroy-region.sh OK 4.16s
> > 9/16 ndctl:cxl / cxl-qos-class.sh OK 3.25s
> > 10/16 ndctl:cxl / cxl-translate.sh OK 0.94s
> > 11/16 ndctl:cxl / cxl-elc.sh OK 4.21s
> > 12/16 ndctl:cxl / cxl-dax-hmem.sh OK 4.56s
> > 13/16 ndctl:cxl / cxl-region-replay.sh OK 8.66s
> > 14/16 ndctl:cxl / cxl-security.sh SKIP 0.02s
> > 15/16 ndctl:cxl / cxl-features.sh OK 1.42s
> > 16/16 ndctl:cxl / cxl-poison.sh SKIP 11.23s
>
> Hi Richard,
>
> Curious about the SKIPs.
>
> I'm running this w the base commit you noted, and no skips, so no
> functional worry. This must be environment. Guessing you're hitting
> the first do_skip of cxl-poison.sh, no CONFIG_TRACING. Maybe the
> keyutils for cxl-security.sh.
>
> Please take a look and see if you can update your environment.
> Poison one is obvious, since this series is touching poison. Security
> one is less obvious, but as Anisa recently showed us w DCD, a seemingly
> unrelated test can uncover latent issues.
>
> -- Alison
>
Hi Alison,
I re-check my machine, and I make cxl-security,sh work now, I missed to install keyutils.
And I do have CONFIG_TRACING turned on, cxl-poison.sh won't work on my machine because
the alignment problem.
On my machine
is_unaligned region2 3
addr=105491107676160
align=805306368
do_skip 'unaligned region not available for testing'
105491107676160 is exactly 805306368 * 130995, so the x3 XOR region lands aligned and there's nothing
unaligned to translate against.
cxl_test anchors its pool at "min(iomem_resource.end + 1 - SZ_64G, mappable.end + 1 - SZ_64G)"
so the window base follows the host memory gap, and no module param moves it.
I'm not sure this is really my setup's environment issue or in fact a test gap ?
If it's the latter I would be happt to fix it in a follow up patch.
Both run_poison_test() rounds pass, so I think everything this series touches is covered, only the unaligned
translation section is unreachable, and this series doesn't touch translation.
Personally I think this is enough prove of test for the serie ? what do you think ?
Best regards,
Richard Cheng.
prev parent reply other threads:[~2026-08-05 3:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 6:48 Richard Cheng
2026-07-31 6:49 ` [PATCH v8 1/3] cxl/region: Simplify poison_by_decoder() error handling Richard Cheng
2026-07-31 19:06 ` Alison Schofield
2026-08-05 3:39 ` Richard Cheng
2026-07-31 6:49 ` [PATCH v8 2/3] cxl/hdm: Allow zero sized HDM decoders Richard Cheng
2026-07-31 6:49 ` [PATCH v8 3/3] tools/testing/cxl: Enable zero sized decoders under hb0 Richard Cheng
2026-07-31 18:52 ` [PATCH v8 0/3] Support zero-sized HDM decoders Alison Schofield
2026-08-05 3:16 ` Richard Cheng [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=anKpY6Y1Sqne1f7Y@MWDK4CY14F \
--to=icheng@nvidia.com \
--cc=alison.schofield@intel.com \
--cc=danwilliams@nvidia.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=djbw@kernel.org \
--cc=iweiny@kernel.org \
--cc=jic23@kernel.org \
--cc=kaihengf@nvidia.com \
--cc=kobak@nvidia.com \
--cc=kristinc@nvidia.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.li@zohomail.com \
--cc=mochs@nvidia.com \
--cc=newtonl@nvidia.com \
--cc=vaslot@nvidia.com \
--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®