From: Dan Williams <dan.j.williams@intel.com>
To: Yao Xingtao <yaoxt.fnst@fujitsu.com>, <dave@stgolabs.net>,
<jonathan.cameron@huawei.com>, <dave.jiang@intel.com>,
<alison.schofield@intel.com>, <vishal.l.verma@intel.com>,
<ira.weiny@intel.com>, <dan.j.williams@intel.com>,
<jim.harris@samsung.com>
Cc: <linux-cxl@vger.kernel.org>, Yao Xingtao <yaoxt.fnst@fujitsu.com>
Subject: Re: [PATCH v7] cxl/region: check interleave capability
Date: Tue, 11 Jun 2024 21:07:09 -0700 [thread overview]
Message-ID: <66691eedbe8_31012947f@dwillia2-xfh.jf.intel.com.notmuch> (raw)
In-Reply-To: <20240612032544.39149-1-yaoxt.fnst@fujitsu.com>
Yao Xingtao wrote:
> Since interleave capability is not verified, if the interleave
> capability of a target does not match the region need, committing decoder
> should have failed at the device end.
>
> In order to checkout this error as quickly as possible, driver needs
> to check the interleave capability of target during attaching it to
> region.
>
> Per CXL specification r3.1(8.2.4.20.1 CXL HDM Decoder Capability Register),
> bits 11 and 12 indicate the capability to establish interleaving in 3, 6,
> 12 and 16 ways. If these bits are not set, the target cannot be attached to
> a region utilizing such interleave ways.
>
> Additionally, bits 8 and 9 represent the capability of the bits used for
> interleaving in the address, Linux tracks this in the cxl_port
> interleave_mask.
>
> Per CXL specification r3.1(8.2.4.20.13 Decoder Protection):
> eIW means encoded Interleave Ways.
> eIG means encoded Interleave Granularity.
>
> in HPA:
> if eIW is 0 or 8 (interleave ways: 1, 3), all the bits of HPA are used,
> the interleave bits are none, the following check is ignored.
>
> if eIW is less than 8 (interleave ways: 2, 4, 8, 16), the interleave bits
> start at bit position eIG + 8 and end at eIG + eIW + 8 - 1.
>
> if eIW is greater than 8 (interleave ways: 6, 12), the interleave bits
> start at bit position eIG + 8 and end at eIG + eIW - 1.
>
> if the interleave mask is insufficient to cover the required interleave
> bits, the target cannot be attached to the region.
>
> Fixes: 384e624bb211 ("cxl/region: Attach endpoint decoders")
> Signed-off-by: Yao Xingtao <yaoxt.fnst@fujitsu.com>
> Reviewed-by: Dan Williams <dan.j.williams@intel.com>
[..]
> diff --git a/drivers/cxl/cxlmem.h b/drivers/cxl/cxlmem.h
> index 36cee9c30ceb..7fe617122d33 100644
> --- a/drivers/cxl/cxlmem.h
> +++ b/drivers/cxl/cxlmem.h
> @@ -848,11 +848,21 @@ static inline void cxl_mem_active_dec(void)
>
> int cxl_mem_sanitize(struct cxl_memdev *cxlmd, u16 cmd);
>
> +/*
Minor detail that can come in a follow-on patch is that this needs to
be:
/**
...in order for the kernel-doc system to autoformat it like it does
other 'struct' documentation:
https://docs.kernel.org/driver-api/cxl/memory-devices.html
However, the reason it needs to be a follow-on patch is that this file
is not currently included for parsing and needs something like this:
diff --git a/Documentation/driver-api/cxl/memory-devices.rst b/Documentation/driver-api/cxl/memory-devices.rst
index 5149ecdc53c7..e33ee67ac1a2 100644
--- a/Documentation/driver-api/cxl/memory-devices.rst
+++ b/Documentation/driver-api/cxl/memory-devices.rst
@@ -325,6 +325,9 @@ CXL Memory Device
.. kernel-doc:: drivers/cxl/pci.c
:internal:
+.. kernel-doc:: drivers/cxl/cxlmem.h
+ :internal:
+
.. kernel-doc:: drivers/cxl/mem.c
:doc: cxl mem
next prev parent reply other threads:[~2024-06-12 4:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 3:25 [PATCH v7] cxl/region: check interleave capability Yao Xingtao
2024-06-12 4:07 ` Dan Williams [this message]
2024-06-12 21:56 ` Alison Schofield
2024-06-13 0:34 ` Xingtao Yao (Fujitsu)
2024-06-13 3:27 ` Dan Williams
2024-06-12 17:04 ` Alison Schofield
2024-06-12 17:45 ` Alison Schofield
2024-06-13 0:31 ` Xingtao Yao (Fujitsu)
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=66691eedbe8_31012947f@dwillia2-xfh.jf.intel.com.notmuch \
--to=dan.j.williams@intel.com \
--cc=alison.schofield@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=ira.weiny@intel.com \
--cc=jim.harris@samsung.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=vishal.l.verma@intel.com \
--cc=yaoxt.fnst@fujitsu.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