From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Yao Xingtao <yaoxt.fnst@fujitsu.com>
Cc: <dave@stgolabs.net>, <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>, <linux-cxl@vger.kernel.org>
Subject: Re: [PATCH v5] cxl/region: check interleave capability
Date: Wed, 5 Jun 2024 14:16:31 +0100 [thread overview]
Message-ID: <20240605141631.00006b54@Huawei.com> (raw)
In-Reply-To: <20240524092740.4260-1-yaoxt.fnst@fujitsu.com>
On Fri, 24 May 2024 05:27:40 -0400
Yao Xingtao <yaoxt.fnst@fujitsu.com> 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.
>
> According to the CXL specification (section 8.2.4.20 CXL HDM Decoder
> Capability Structure), bits 11 and 12 within the 'CXL HDM Decoder
> Capability Register' 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 in the same register represent the capability
> of the bits used for interleaving in the address, Linux tracks this in the
> cxl_port interleave_mask.
>
> Regarding 'Decoder Protection':
> If IW is less than 8 (for interleave ways of 1, 2, 4, 8, 16), the
> interleave bits start at bit position IG + 8 and end at IG + IW + 8 - 1.
>
> If the IW is greater than or equal to 8 (for interleave ways of 3, 6, 12),
> the interleave bits start at bit position IG + 8 and end at IG + IW - 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>
Hi Yao,
A few comments inline.
Jonathan
> ---
> drivers/cxl/core/hdm.c | 10 +++++
> drivers/cxl/core/region.c | 83 +++++++++++++++++++++++++++++++++++++++
> drivers/cxl/cxl.h | 2 +
> drivers/cxl/cxlmem.h | 1 +
> 4 files changed, 96 insertions(+)
>
> static bool should_emulate_decoders(struct cxl_endpoint_dvsec_info *info)
> diff --git a/drivers/cxl/core/region.c b/drivers/cxl/core/region.c
> index 5c186e0a39b9..6b7400313cb2 100644
> --- a/drivers/cxl/core/region.c
> +++ b/drivers/cxl/core/region.c
> @@ -1054,6 +1054,7 @@ static int cxl_port_attach_region(struct cxl_port *port,
> struct cxl_decoder *cxld;
> unsigned long index;
> int rc = -EBUSY;
> + struct cxl_switch_decoder *cxlsd;
Could reduces scope of this...
>
> lockdep_assert_held_write(&cxl_region_rwsem);
>
> @@ -1101,6 +1102,23 @@ static int cxl_port_attach_region(struct cxl_port *port,
> }
> cxld = cxl_rr->decoder;
>
> + /*
> + * the number of targets should not exceed the target_count
> + * of the decoder
> + */
> + if (is_switch_decoder(&cxld->dev)) {
struct cxl_switch_decoder *cxlsd =
to_switch_decoder(&cxld->dev);
> + cxlsd = to_cxl_switch_decoder(&cxld->dev);
> + if (cxl_rr->nr_targets > cxlsd->nr_targets) {
> + dev_dbg(&cxlr->dev,
> + "%s:%s %s add: %s:%s @ %d overflows targets: %d\n",
> + dev_name(port->uport_dev), dev_name(&port->dev),
> + dev_name(&cxld->dev), dev_name(&cxlmd->dev),
> + dev_name(&cxled->cxld.dev), pos,
> + cxlsd->nr_targets);
set rc?
> + goto out_erase;
> + }
> + }
> +
> rc = cxl_rr_ep_add(cxl_rr, cxled);
> if (rc) {
> dev_dbg(&cxlr->dev,
> @@ -1210,6 +1228,53 @@ static int check_last_peer(struct cxl_endpoint_decoder *cxled,
> return 0;
> }
>
> +static int check_interleave_cap(struct cxl_decoder *cxld, int iw, int ig)
> +{
> + struct cxl_port *port = to_cxl_port(cxld->dev.parent);
> + struct cxl_hdm *cxlhdm = dev_get_drvdata(&port->dev);
> + unsigned int interleave_mask;
> + u8 eiw;
> + u16 eig;
> + int rc, high_pos, low_pos;
> +
> + rc = ways_to_eiw(iw, &eiw);
> + if (rc)
> + return rc;
> +
> + if (!test_bit(iw, &cxlhdm->iw_cap_mask))
> + return -ENXIO;
> +
> + rc = granularity_to_eig(ig, &eig);
> + if (rc)
> + return rc;
> +
> + /*
> + * Per CXL specification (8.2.3.20.13 Decoder Protection in r3.1)
8.2.4.20.13 I think
> + * if eiw < 8, the interleave bits start at bit position eig + 8, and
> + * end at eig + eiw + 8 - 1.
> + * if eiw >= 8, the interleave bits start at bit position eig + 8, and
> + * end at eig + eiw - 1.
> + */
> + if (eiw >= 8)
> + high_pos = eiw + eig - 1;
> + else
> + high_pos = eiw + eig + 7;
> + low_pos = eig + 8;
> + /*
> + * when the eiw is 0 or 8 (interlave way is 1 or 3), the num of
interleave
> + * interleave bits is 0, there is no interleaving, the following
> + * check is ignored.
If the interleave is 3 there is no interleave? That seems an odd statement
perhaps make that comment more detailed.
My understanding is that it's just more complex and all bits are relevant.
> + */
> + if (low_pos > high_pos)
> + return 0;
> +
> + interleave_mask = GENMASK(high_pos, low_pos);
> + if (interleave_mask & ~cxlhdm->interleave_mask)
> + return -ENXIO;
> +
> + return 0;
> +}
> +
> static int cxl_port_setup_targets(struct cxl_port *port,
> struct cxl_region *cxlr,
> struct cxl_endpoint_decoder *cxled)
> @@ -1360,6 +1425,15 @@ static int cxl_port_setup_targets(struct cxl_port *port,
> return -ENXIO;
> }
> } else {
> + rc = check_interleave_cap(cxld, iw, ig);
> + if (rc) {
> + dev_dbg(&cxlr->dev,
> + "%s:%s iw: %d ig: %d is not supported\n",
> + dev_name(port->uport_dev),
> + dev_name(&port->dev), iw, ig);
> + return rc;
> + }
> +
> cxld->interleave_ways = iw;
> cxld->interleave_granularity = ig;
> cxld->hpa_range = (struct range) {
> @@ -1796,6 +1870,15 @@ static int cxl_region_attach(struct cxl_region *cxlr,
> struct cxl_dport *dport;
> int rc = -ENXIO;
>
> + rc = check_interleave_cap(&cxled->cxld, p->interleave_ways,
> + p->interleave_granularity);
> + if (rc) {
> + dev_dbg(&cxlr->dev, "%s iw: %d ig: %d is not supported\n",
> + dev_name(&cxled->cxld.dev), p->interleave_ways,
> + p->interleave_granularity);
> + return rc;
> + }
> +
> if (cxled->mode != cxlr->mode) {
> dev_dbg(&cxlr->dev, "%s region mode: %d mismatch: %d\n",
> dev_name(&cxled->cxld.dev), cxlr->mode, cxled->mode);
next prev parent reply other threads:[~2024-06-05 13:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-24 9:27 [PATCH v5] cxl/region: check interleave capability Yao Xingtao
2024-06-05 13:16 ` Jonathan Cameron [this message]
2024-06-06 2:19 ` Xingtao Yao (Fujitsu)
2024-06-10 10:25 ` Jonathan Cameron
2024-06-05 15:55 ` Alison Schofield
2024-06-06 3:46 ` Xingtao Yao (Fujitsu)
2024-06-10 10:36 ` Jonathan Cameron
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=20240605141631.00006b54@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=ira.weiny@intel.com \
--cc=jim.harris@samsung.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