From: Dan Williams <dan.j.williams@intel.com>
To: Jim Harris <jim.harris@samsung.com>,
"dan.j.williams@intel.com" <dan.j.williams@intel.com>,
"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>
Subject: RE: [PATCH v2] cxl/region: use region (not root decoder) granularity for calculations
Date: Thu, 26 Oct 2023 10:11:38 -0700 [thread overview]
Message-ID: <653a9dca299ef_244c8f294d9@dwillia2-xfh.jf.intel.com.notmuch> (raw)
In-Reply-To: <169824893473.1403938.16110924262989774582.stgit@bgt-140510-bm03.eng.stellus.in>
Jim Harris wrote:
> Root decoder granularity must match value from CFWMS, which may not
> be the region's granularity for non-interleaved root decoders.
>
> So when calculating granularities for host bridge decoders, use the
> region's granularity instead of the root decoder's granularity to ensure
> the correct granularities are set for the host bridge decoders and any
> downstream switch decoders.
>
> Test configuration is 1 host bridge * 2 switches * 2 endpoints per switch.
>
> Region created with 2048 granularity using following command line:
>
> cxl create-region -m -d decoder0.0 -w 4 mem0 mem2 mem1 mem3 \
> -g 2048 -s 2048M
>
> Use "cxl list -PDE | grep granularity" to get a view of the granularity
> set at each level of the topology.
>
> Before this patch:
> "interleave_granularity":2048,
> "interleave_granularity":2048,
> "interleave_granularity":512,
> "interleave_granularity":2048,
> "interleave_granularity":2048,
> "interleave_granularity":512,
> "interleave_granularity":256,
>
> After:
> "interleave_granularity":2048,
> "interleave_granularity":2048,
> "interleave_granularity":4096,
> "interleave_granularity":2048,
> "interleave_granularity":2048,
> "interleave_granularity":4096,
> "interleave_granularity":2048,
>
> Signed-off-by: Jim Harris <jim.harris@samsung.com>
> ---
> drivers/cxl/core/region.c | 9 ++++++++-
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/cxl/core/region.c b/drivers/cxl/core/region.c
> index 6d63b8798c29..c25be26d0bdf 100644
> --- a/drivers/cxl/core/region.c
> +++ b/drivers/cxl/core/region.c
> @@ -1133,7 +1133,14 @@ static int cxl_port_setup_targets(struct cxl_port *port,
> }
>
> if (is_cxl_root(parent_port)) {
> - parent_ig = cxlrd->cxlsd.cxld.interleave_granularity;
> + /*
> + * Root decoder IG is always set to value in CFMWS which
> + * may be different than this region's IG. We can use the
> + * region's IG here since interleave_granularity_store()
> + * does not allow interleaved host-bridges with
> + * root IG != region IG.
> + */
> + parent_ig = p->interleave_granularity;
> parent_iw = cxlrd->cxlsd.cxld.interleave_ways;
This causes the kernel to correctly detect that cxl_test was programming
an incorrect host-bridge level granularity value. Fixup the test.
diff --git a/tools/testing/cxl/test/cxl.c b/tools/testing/cxl/test/cxl.c
index fb6ab9cef84f..b88546299902 100644
--- a/tools/testing/cxl/test/cxl.c
+++ b/tools/testing/cxl/test/cxl.c
@@ -831,7 +831,7 @@ static void mock_init_hdm_decoder(struct cxl_decoder *cxld)
cxld->interleave_ways = 2;
else
cxld->interleave_ways = 1;
- cxld->interleave_granularity = 256;
+ cxld->interleave_granularity = 4096;
cxld->hpa_range = (struct range) {
.start = base,
.end = base + size - 1,
prev parent reply other threads:[~2023-10-26 17:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20231004230826uscas1p2f7957bf868a609211271e30ad8ff551f@uscas1p2.samsung.com>
2023-10-04 23:08 ` [PATCH] cxl: set root decoder granularity based on region params Jim Harris
2023-10-05 1:18 ` Dan Williams
2023-10-05 16:52 ` Jim Harris
2023-10-05 18:08 ` Dan Williams
2023-10-25 0:55 ` Dan Williams
2023-10-25 1:33 ` Jim Harris
2023-10-25 1:58 ` Dan Williams
2023-10-06 16:21 ` [PATCH] cxl/region: use region (not root decoder) granularity for calculations Jim Harris
2023-10-25 2:11 ` Dan Williams
2023-10-25 15:48 ` Jim Harris
2023-10-25 15:48 ` [PATCH v2] " Jim Harris
2023-10-26 0:11 ` Dan Williams
2023-10-26 17:11 ` Dan Williams [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=653a9dca299ef_244c8f294d9@dwillia2-xfh.jf.intel.com.notmuch \
--to=dan.j.williams@intel.com \
--cc=jim.harris@samsung.com \
--cc=linux-cxl@vger.kernel.org \
/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