From: Dave Jiang <dave.jiang@intel.com>
To: Alison Schofield <alison.schofield@intel.com>,
Davidlohr Bueso <dave@stgolabs.net>,
Jonathan Cameron <jic23@kernel.org>,
Vishal Verma <vishal.l.verma@intel.com>,
Ira Weiny <iweiny@kernel.org>, Li Ming <ming.li@zohomail.com>
Cc: linux-cxl@vger.kernel.org
Subject: Re: [PATCH v3 0/2] cxl: Allow passthrough decoders with >16K granularity
Date: Mon, 27 Jul 2026 16:36:59 -0700 [thread overview]
Message-ID: <9b3d1137-bc36-4abb-9b29-c17b0efe64ef@intel.com> (raw)
In-Reply-To: <cover.1784940306.git.alison.schofield@intel.com>
On 7/24/26 6:08 PM, Alison Schofield wrote:
> Changes in v3:
> - Program the real IG encoding for an encodable non-interleaving granularity
> instead of always writing EIG=0 (RichardC, Sashiko)
> - Update Patch 1 commit msg text and this cover letter text per above change
> Link to v2:
> https://lore.kernel.org/linux-cxl/cover.1783795720.git.alison.schofield@intel.com/
>
For the series:
Reviewed-by: Dave Jiang <dave.jiang@intel.com>
DJ
> Changes in v2:
> - Rebased on Linux 7.2-rc1
> - Only v1 feedback was from Sashiko and that was not an issue
> Link to v1:
> https://lore.kernel.org/linux-cxl/cover.1781136281.git.alison.schofield@intel.com/
>
> Sashiko reported [1] that region setup rejects valid topologies
> containing a passthrough decoder beneath a wide parent interleave. In
> these configurations, a passthrough decoder can compute a granularity
> above the 16K maximum encodable in the interleave granularity (IG)
> field even though non-interleaving decoders do not consume that field.
>
> The first patch avoids validating the interleave granularity of
> non-interleaving decoders, encodes the IG field as a don't-care
> only when the computed granularity is not encodable, and updates
> the sysfs ABI documentation accordingly.
>
> The second patch extends cxl-test with a topology that allows a CXL
> unit test to cover this case.
>
> A unit test update for this case is posted for review [2].
>
> [1] https://lore.kernel.org/all/20260530002613.682E71F00893@smtp.kernel.org/
> [2] https://lore.kernel.org/all/cover.1781136221.git.alison.schofield@intel.com/
>
>
> Alison Schofield (2):
> cxl/region: Allow passthrough decoders with >16K granularity
> cxl/test: Add a 2-way 16K root decoder for passthrough testing
>
> Documentation/ABI/testing/sysfs-bus-cxl | 5 ++-
> drivers/cxl/core/hdm.c | 8 ++++-
> drivers/cxl/core/region.c | 47 ++++++++++++++----------
> tools/testing/cxl/test/cxl.c | 48 +++++++++++++++++++++++--
> 4 files changed, 85 insertions(+), 23 deletions(-)
>
>
> base-commit: dc59e4fea9d83f03bad6bddf3fa2e52491777482
prev parent reply other threads:[~2026-07-27 23:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-25 1:08 [PATCH v3 0/2] cxl: Allow passthrough decoders with >16K granularity Alison Schofield
2026-07-25 1:08 ` [PATCH v3 1/2] cxl/region: " Alison Schofield
2026-07-25 1:26 ` sashiko-bot
2026-07-25 1:42 ` Alison Schofield
2026-07-31 7:41 ` Richard Cheng
2026-09-04 3:17 ` Alison Schofield
2026-07-25 1:08 ` [PATCH v3 2/2] cxl/test: Add a 2-way 16K root decoder for passthrough testing Alison Schofield
2026-07-31 7:44 ` Richard Cheng
2026-09-04 3:12 ` Alison Schofield
2026-07-27 23:36 ` Dave Jiang [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=9b3d1137-bc36-4abb-9b29-c17b0efe64ef@intel.com \
--to=dave.jiang@intel.com \
--cc=alison.schofield@intel.com \
--cc=dave@stgolabs.net \
--cc=iweiny@kernel.org \
--cc=jic23@kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=ming.li@zohomail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.