Linux CXL
 help / color / mirror / Atom feed
From: Dave Jiang <dave.jiang@intel.com>
To: Richard Cheng <icheng@nvidia.com>,
	dave@stgolabs.net, jic23@kernel.org, alison.schofield@intel.com,
	vishal.l.verma@intel.com, ira.weiny@intel.com, djbw@kernel.org,
	shiju.jose@huawei.com, ming.li@zohomail.com
Cc: alucerop@amd.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: [PATCH RESEND] tools/testing/cxl: Resolve auto-region decoder targets like real HW
Date: Thu, 11 Jun 2026 18:53:56 -0700	[thread overview]
Message-ID: <f678ebb7-ec1b-4e48-b0ed-d223566ffe7e@intel.com> (raw)
In-Reply-To: <20260612011227.4220-1-icheng@nvidia.com>



On 6/11/26 6:12 PM, Richard Cheng wrote:
> The mock auto-region created at module load wrote switch and host-bridge
> decoder target[] directly, in addition to target_map[]. Real HW programs
> only target_map[] and resolves target[] as dports enumerate, via
> update_decoder_targets(). Region replay already follows that ordering,
> the initial auto-region did not.
> 
> Drop the direct target[] writes and call
> cxl_port_update_decoder_targets() so target[] is resolved the same way
> as real HW and region replay, exercising more of the auto-region driver
> path.
> 
> This is inspired by the discussion [1] below:
> 
> [1]: https://lore.kernel.org/all/20260521084806.28232-1-icheng@nvidia.com/
> Suggested-by: Alison Schofield <alison.schofield@intel.com>
> Signed-off-by: Richard Cheng <icheng@nvidia.com>

Reviewed-by: Dave Jiang <dave.jiang@intel.com>
Tested-by: Dave Jiang <dave.jiang@intel.com>

> ---
> cxl_mock_mem didn't load together when I manually modprobe cxl_test
> module, should we make them loaded together automatically for better
> user experience?
> 
> Best regards,
> Richard Cheng.
> ---
>  tools/testing/cxl/test/cxl.c | 18 ++++++++++++------
>  1 file changed, 12 insertions(+), 6 deletions(-)
> 
> diff --git a/tools/testing/cxl/test/cxl.c b/tools/testing/cxl/test/cxl.c
> index 418669927fb0..5266aa3733cb 100644
> --- a/tools/testing/cxl/test/cxl.c
> +++ b/tools/testing/cxl/test/cxl.c
> @@ -1181,15 +1181,11 @@ static bool mock_init_hdm_decoder(struct cxl_decoder *cxld)
>  		cxlsd = to_cxl_switch_decoder(dev);
>  		if (i == 0) {
>  			/* put cxl_mem.4 second in the decode order */
> -			if (pdev->id == 4) {
> -				cxlsd->target[1] = dport;
> +			if (pdev->id == 4)
>  				cxlsd->cxld.target_map[1] = dport->port_id;
> -			} else {
> -				cxlsd->target[0] = dport;
> +			else
>  				cxlsd->cxld.target_map[0] = dport->port_id;
> -			}
>  		} else {
> -			cxlsd->target[0] = dport;
>  			cxlsd->cxld.target_map[0] = dport->port_id;
>  		}
>  		cxld = &cxlsd->cxld;
> @@ -1212,6 +1208,16 @@ static bool mock_init_hdm_decoder(struct cxl_decoder *cxld)
>  		cxld->commit = mock_decoder_commit;
>  		cxld->reset = mock_decoder_reset;
>  
> +		/*
> +		 * Only target_map[] is programmed above, mimicking
> +		 * firmware. On real hardware target[] is populated as
> +		 * dports enumerate, via update_decoder_targets(). The
> +		 * mock's dports are already bound by now, so fire that
> +		 * resolution explicitly here rather than stamping
> +		 * target[] directly.
> +		 */
> +		cxl_port_update_decoder_targets(iter, dport);
> +
>  		cxld_registry_update(cxld);
>  		put_device(dev);
>  	}


  reply	other threads:[~2026-06-12  1:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-12  1:12 [PATCH RESEND] tools/testing/cxl: Resolve auto-region decoder targets like real HW Richard Cheng
2026-06-12  1:53 ` Dave Jiang [this message]
2026-06-12  5:41 ` Alison Schofield
2026-06-12 16:39 ` Dave Jiang

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=f678ebb7-ec1b-4e48-b0ed-d223566ffe7e@intel.com \
    --to=dave.jiang@intel.com \
    --cc=alison.schofield@intel.com \
    --cc=alucerop@amd.com \
    --cc=dave@stgolabs.net \
    --cc=djbw@kernel.org \
    --cc=icheng@nvidia.com \
    --cc=ira.weiny@intel.com \
    --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=newtonl@nvidia.com \
    --cc=shiju.jose@huawei.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