Linux CXL
 help / color / mirror / Atom feed
From: Alison Schofield <alison.schofield@intel.com>
To: Richard Cheng <icheng@nvidia.com>
Cc: <dave@stgolabs.ne>, <jonathan.cameron@huawei.com>,
	<dave.jiang@intel.com>, <vishal.l.verma@intel.com>,
	<ira.weiny@intel.com>, <dan.j.williams@intel.com>,
	<fabio.m.de.francesco@linux.intel.com>, <rrichter@amd.com>,
	<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>
Subject: Re: [RFC PATCH] tools/testing/cxl: Support multi-decoder shared-dport topology
Date: Wed, 27 May 2026 18:40:29 -0700	[thread overview]
Message-ID: <ahedDZFbtaMUqeBM@aschofie-mobl2.lan> (raw)
In-Reply-To: <ahAvg9I9geuaBrEK@MWDK4CY14F>

On Fri, May 22, 2026 at 06:31:49PM +0800, Richard Cheng wrote:
> On Thu, May 21, 2026 at 06:29:22PM +0800, Alison Schofield wrote:
> > On Thu, May 21, 2026 at 04:48:06PM +0800, Richard Cheng wrote:

big snip

> Hi Alison, thanks for the suggestion and I think this script is a better solution
> then my patch, though I would like to ask can you provide the implementation of
> reply_regions() here? it seems like a missing piece for me that I can't execute
> this script on my machine.

replay_region support first appeared in kernel 7.1-rc1
f3b1d2260703 tools/testing/cxl: Enable replay of user regions as auto regions

and the tooling support is on the ndctl pending branch:
https://github.com/pmem/ndctl/tree/pending
ccc1955b697f test/common: add helpers for CXL region replay testing
81c7cdd6cbcb test/cxl-region-replay.sh: add test of region replay workflow

> 
> Secondly, I want to make sure do you have any decoder with targets, and with some decoder
> without targets ? I wonder your filter might report that case as buggy as well.

The filter only catches the specific signature (1+7) of the bug Robert fixed.
Other mixes like 2+5 aren't expected from this bug or from a correct kernel,
so the test isn't designed to catch them. If a future regression produced a
different ratio, this test wouldn't notice.

-- Alison

> 
> But the overall intention I can see this can be reproduce by the current infrastructure.
> 
> And yes I'll spend time to work on the region replay gap, I'll send patches once I finish the
> work.
> 
> Best regards,
> Richard Cheng.
> 
snip

  reply	other threads:[~2026-05-28  1:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-21  8:48 [RFC PATCH] tools/testing/cxl: Support multi-decoder shared-dport topology Richard Cheng
2026-05-21 16:02 ` Dave Jiang
2026-05-22  1:29 ` Alison Schofield
2026-05-22 10:31   ` Richard Cheng
2026-05-28  1:40     ` Alison Schofield [this message]
2026-05-29  5:30   ` Alison Schofield
2026-06-04 10:12     ` Richard Cheng

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=ahedDZFbtaMUqeBM@aschofie-mobl2.lan \
    --to=alison.schofield@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=dave@stgolabs.ne \
    --cc=fabio.m.de.francesco@linux.intel.com \
    --cc=icheng@nvidia.com \
    --cc=ira.weiny@intel.com \
    --cc=jonathan.cameron@huawei.com \
    --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=newtonl@nvidia.com \
    --cc=rrichter@amd.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