All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: <linux-cxl@vger.kernel.org>, <rrichter@amd.com>
Subject: Re: [PATCH v2 1/3] cxl/mem: Quiet port walking warnings
Date: Thu, 26 Jan 2023 10:02:35 +0000	[thread overview]
Message-ID: <20230126100235.00000d6c@Huawei.com> (raw)
In-Reply-To: <167468465444.586774.9409731200278259584.stgit@dwillia2-xfh.jf.intel.com>

On Wed, 25 Jan 2023 14:11:17 -0800
Dan Williams <dan.j.williams@intel.com> wrote:

> The cxl_mem driver attempts to establish, or revalidate, the cxl_port
> hierarcy to attach a cxl_memdev to a CXL platform topology. There is a
> natural race (on ACPI platforms) between when the cxl_mem driver
> attempts to attach and when the cxl_acpi driver establishes the root of
> the topology.
> 
> If cxl_mem_probe() runs first it will iterate to the top of the device
> topology without finding the CXL platform root. That situation is benign
> / expected, so stop warning about it. The cxl_acpi driver will poke
> cxl_mem_probe() to try again once the CXL platform root is established.
> 
> Suppress any upper level errors by making it clear that this is merely a
> probe deferral event, not a hard error.
> 
> Signed-off-by: Dan Williams <dan.j.williams@intel.com>

Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>

> ---
> Changes since v1:
> * Use dev_err_probe() (Jonathan)
> 
>  drivers/cxl/core/port.c |    7 ++++---
>  1 file changed, 4 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/cxl/core/port.c b/drivers/cxl/core/port.c
> index b631a0520456..feb8f84a9281 100644
> --- a/drivers/cxl/core/port.c
> +++ b/drivers/cxl/core/port.c
> @@ -1397,9 +1397,10 @@ int devm_cxl_enumerate_ports(struct cxl_memdev *cxlmd)
>  
>  		uport_dev = dport_dev->parent;
>  		if (!uport_dev) {
> -			dev_warn(dev, "at %s no parent for dport: %s\n",
> -				 dev_name(iter), dev_name(dport_dev));
> -			return -ENXIO;
> +			dev_err_probe(dev, -EPROBE_DEFER,
> +				      "at %s no parent for dport: %s\n",
> +				      dev_name(iter), dev_name(dport_dev));
> +			return -EPROBE_DEFER;
>  		}
>  
>  		dev_dbg(dev, "scan: iter: %s dport_dev: %s parent: %s\n",
> 


  reply	other threads:[~2023-01-26 10:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-17  1:33 [PATCH 0/3] cxl: Misc fixups that missed v6.2 Dan Williams
2022-12-17  1:33 ` [PATCH 1/3] cxl/mem: Quiet port walking warning Dan Williams
2023-01-03 10:49   ` Robert Richter
2023-01-03 21:07     ` Dan Williams
2023-01-04  9:36       ` Robert Richter
2023-01-13 11:04         ` Jonathan Cameron
2023-01-25 21:09           ` Dan Williams
2023-01-25 22:11           ` [PATCH v2 1/3] cxl/mem: Quiet port walking warnings Dan Williams
2023-01-26 10:02             ` Jonathan Cameron [this message]
2023-01-26 11:47             ` Robert Richter
2022-12-17  1:33 ` [PATCH 2/3] cxl/region: Clarify when a cxld->commit() callback is mandatory Dan Williams
2023-01-13 11:24   ` Jonathan Cameron
2023-01-25 22:44     ` Dan Williams
2022-12-17  1:33 ` [PATCH 3/3] cxl/port: Link the 'parent_dport' in portX/ and endpointX/ sysfs Dan Williams
2023-01-13 11:39   ` Jonathan Cameron
2023-01-25 22:46     ` Dan Williams
2023-01-25 23:32       ` Dan Williams

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=20230126100235.00000d6c@Huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=dan.j.williams@intel.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=rrichter@amd.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.