From: Alison Schofield <alison.schofield@intel.com>
To: Robert Richter <rrichter@amd.com>
Cc: Davidlohr Bueso <dave@stgolabs.net>,
Jonathan Cameron <jic23@kernel.org>,
Dave Jiang <dave.jiang@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Ira Weiny <iweiny@kernel.org>, Li Ming <ming.li@zohomail.com>,
<linux-cxl@vger.kernel.org>,
Jonathan Cameron <jonathan.cameron@oss.qualcomm.com>
Subject: Re: [PATCH v5 2/7] cxl/region: Warn on user region position mismatch
Date: Fri, 18 Sep 2026 14:18:13 -0700 [thread overview]
Message-ID: <aq2qlauyD3qSosT8@aschofie-mobl2.lan> (raw)
In-Reply-To: <aqqF98W7MnnDTTet@rric.localdomain>
On Wed, Sep 16, 2026 at 02:05:11PM +0200, Robert Richter wrote:
> On 03.09.26 16:23:44, Alison Schofield wrote:
> > User region creation includes a self-test that checks the assigned endpoint
> > positions against the position calculation used by auto region creation.
> > The result, matching or not, is reported with dev_dbg().
>
> As commented to the doc, the position is clearly defined as the bit
> mask that is striped off by the endpoint. That should be documented in
> the code to describe, what position means in that context, esp. how
> the position in the target list of each level adds to the position.
> That clarity is missing.
Agreed that position could use a clearer definition. Patch 3 updates the
cxl_calc_interleave_pos() documentation, so I'll address this there in v6,
along with the documentation changes discussed in patch 1
-- Alison
>
> >
> > Promote that to a dev_warn() that fires only on a mismatch, so bugs in the
> > auto region position calculation are easier to catch as that calculation is
> > extended to support more region configurations.
>
> dev_warn() change looks good to me.
>
> >
> > The matching case no longer prints, so dynamic debug on region.c no longer
> > confirms that the self-test ran.
> >
> > Signed-off-by: Alison Schofield <alison.schofield@intel.com>
> > Reviewed-by: Jonathan Cameron <jonathan.cameron@oss.qualcomm.com>
>
> Reviewed-by: Robert Richter <rrichter@amd.com>
next prev parent reply other threads:[~2026-09-18 21:18 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 23:23 [PATCH v5 0/7] cxl: Support mixed-granularity region interleaves Alison Schofield
2026-09-03 23:23 ` [PATCH v5 1/7] Documentation/cxl: Describe mixed-granularity regions Alison Schofield
2026-09-07 23:23 ` Jonathan Cameron
2026-09-16 11:51 ` Robert Richter
2026-09-18 20:48 ` Alison Schofield
2026-09-03 23:23 ` [PATCH v5 2/7] cxl/region: Warn on user region position mismatch Alison Schofield
2026-09-16 12:05 ` Robert Richter
2026-09-18 21:18 ` Alison Schofield [this message]
2026-09-25 0:30 ` Alison Schofield
2026-09-03 23:23 ` [PATCH v5 3/7] cxl/region: Generalize endpoint position mapping Alison Schofield
2026-09-07 23:42 ` Jonathan Cameron
2026-09-18 23:01 ` Alison Schofield
2026-09-16 14:15 ` Robert Richter
2026-09-18 23:20 ` Alison Schofield
2026-09-03 23:23 ` [PATCH v5 4/7] cxl/region: Name the interleave locals in cxl_port_setup_targets() Alison Schofield
2026-09-07 23:50 ` [PATCH v5 4/7] cxo_ol/region: " Jonathan Cameron
2026-09-19 0:42 ` Alison Schofield
2026-09-16 14:34 ` [PATCH v5 4/7] cxl/region: " Robert Richter
2026-09-16 17:45 ` Robert Richter
2026-09-19 0:58 ` Alison Schofield
2026-09-19 0:55 ` Alison Schofield
2026-09-03 23:23 ` [PATCH v5 5/7] cxl/region: Support mixed-granularity auto regions Alison Schofield
2026-09-08 0:02 ` Jonathan Cameron
2026-09-16 18:03 ` Robert Richter
2026-09-03 23:23 ` [PATCH v5 6/7] cxl/region: Support mixed-granularity user created regions Alison Schofield
2026-09-08 0:03 ` Jonathan Cameron
2026-09-16 18:13 ` Robert Richter
2026-09-03 23:23 ` [PATCH v5 7/7] cxl/test: Add a topology to test mixed-granularity regions Alison Schofield
2026-09-08 0:10 ` Jonathan Cameron
2026-09-16 18:19 ` [PATCH v5 0/7] cxl: Support mixed-granularity region interleaves Robert Richter
2026-09-18 19:49 ` Alison Schofield
2026-09-29 22:48 ` 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=aq2qlauyD3qSosT8@aschofie-mobl2.lan \
--to=alison.schofield@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=iweiny@kernel.org \
--cc=jic23@kernel.org \
--cc=jonathan.cameron@oss.qualcomm.com \
--cc=linux-cxl@vger.kernel.org \
--cc=ming.li@zohomail.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