From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: <alison.schofield@intel.com>
Cc: Davidlohr Bueso <dave@stgolabs.net>,
Dave Jiang <dave.jiang@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Ira Weiny <ira.weiny@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
<linux-cxl@vger.kernel.org>
Subject: Re: [PATCH v3] cxl/region: Match auto-discovered region decoders by HPA range
Date: Wed, 13 Sep 2023 17:31:59 +0100 [thread overview]
Message-ID: <20230913173159.00007124@Huawei.com> (raw)
In-Reply-To: <20230905211007.256385-1-alison.schofield@intel.com>
On Tue, 5 Sep 2023 14:10:07 -0700
alison.schofield@intel.com wrote:
> From: Alison Schofield <alison.schofield@intel.com>
>
> Currently, when the region driver attaches a region to a port, it
> selects the ports next available decoder to program.
>
> With the addition of auto-discovered regions, a port decoder has
> already been programmed so grabbing the next available decoder can
> be a mismatch when there is more than one region using the port.
>
> The failure appears like this with CXL DEBUG enabled:
>
> [] cxl_core:alloc_region_ref:754: cxl region0: endpoint9: HPA order violation region0:[mem 0x14780000000-0x1478fffffff flags 0x200] vs [mem 0x880000000-0x185fffffff flags 0x200]
> [] cxl_core:cxl_port_attach_region:972: cxl region0: endpoint9: failed to allocate region reference
>
> When CXL DEBUG is not enabled, there is no failure message. The region
> just never materializes. Users can suspect this issue if they know their
> firmware has programmed decoders so that more than one region is using
> a port. Note that the problem may appear intermittently, ie not on
> every reboot.
>
> Add a matching method for auto-discovered regions that finds a decoder
> based on an HPA range. The decoder range must exactly match the region
> resource parameter.
>
> Fixes: a32320b71f08 ("cxl/region: Add region autodiscovery")
> Signed-off-by: Alison Schofield <alison.schofield@intel.com>
> Reviewed-by: Dave Jiang <dave.jiang@intel.com>
> Reviewed-by: Davidlohr Bueso <dave@stgolabs.net>
LGTM as addressed only thing I found in v2.
Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> ---
>
> Changes in v3:
> - Update match_auto_decoder() to simply return 1 if found, 0 if not found.
> Conflict resolution is already done in cxl_rr_alloc_decoder()
> (Jonathan, Dan)
> - Add Reviewed-by tags (DaveJ, Davidlohr)
> - v2: https://lore.kernel.org/linux-cxl/20230822014303.110509-1-alison.schofield@intel.com/
>
> Changes in v2:
> - Use cxlr->params for HPA match rather than requiring cxled (Dan)
> - dev_warn() if decoder already assigned to a region (Dan)
> - Add failure footprint to commit log (Dan)
> - Add Fixes Tag (Dan)
> - v1: https://lore.kernel.org/linux-cxl/20230804213004.1669658-1-alison.schofield@intel.com/
>
>
> drivers/cxl/core/region.c | 24 +++++++++++++++++++++++-
> 1 file changed, 23 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/cxl/core/region.c b/drivers/cxl/core/region.c
> index e115ba382e04..b4c6a749406f 100644
> --- a/drivers/cxl/core/region.c
> +++ b/drivers/cxl/core/region.c
> @@ -717,13 +717,35 @@ static int match_free_decoder(struct device *dev, void *data)
> return 0;
> }
>
> +static int match_auto_decoder(struct device *dev, void *data)
> +{
> + struct cxl_region_params *p = data;
> + struct cxl_decoder *cxld;
> + struct range *r;
> +
> + if (!is_switch_decoder(dev))
> + return 0;
> +
> + cxld = to_cxl_decoder(dev);
> + r = &cxld->hpa_range;
> +
> + if (p->res && p->res->start == r->start && p->res->end == r->end)
> + return 1;
> +
> + return 0;
> +}
> +
> static struct cxl_decoder *cxl_region_find_decoder(struct cxl_port *port,
> struct cxl_region *cxlr)
> {
> struct device *dev;
> int id = 0;
>
> - dev = device_find_child(&port->dev, &id, match_free_decoder);
> + if (test_bit(CXL_REGION_F_AUTO, &cxlr->flags))
> + dev = device_find_child(&port->dev, &cxlr->params,
> + match_auto_decoder);
> + else
> + dev = device_find_child(&port->dev, &id, match_free_decoder);
> if (!dev)
> return NULL;
> /*
>
> base-commit: fe77cc2e5a6a7c85f5c6ef8a39d7694ffc7f41c9
prev parent reply other threads:[~2023-09-13 16:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 21:10 [PATCH v3] cxl/region: Match auto-discovered region decoders by HPA range alison.schofield
2023-09-13 16:31 ` Jonathan Cameron [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=20230913173159.00007124@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=linux-cxl@vger.kernel.org \
--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