From: Gregory Price <gourry@gourry.net>
To: Dan Williams <dan.j.williams@intel.com>
Cc: linux-cxl@vger.kernel.org, linux-kernel@vger.kernel.org,
dave@stgolabs.net, jonathan.cameron@huawei.com,
dave.jiang@intel.com, alison.schofield@intel.com,
vishal.l.verma@intel.com, ira.weiny@intel.com, rrichter@amd.com,
terry.bowman@amd.com
Subject: Re: [PATCH] cxl/core/port: defer probe when memdev fails to find correct port
Date: Tue, 1 Oct 2024 11:20:11 -0400 [thread overview]
Message-ID: <ZvwTKxTc9yDypmkG@PC2K9PVX.TheFacebook.com> (raw)
In-Reply-To: <ZurAiwt7t2WWVrJM@PC2K9PVX.TheFacebook.com>
On Wed, Sep 18, 2024 at 01:59:07PM +0200, Gregory Price wrote:
> On Fri, Sep 13, 2024 at 09:32:48PM -0700, Dan Williams wrote:
> > Gregory Price wrote:
> > > Depending on device/hierarchy readiness, it can be possible for the
> > > async probe process to attempt to register an endpoint before the
> > > entire port hierarchy is ready. This currently fails with -ENXIO.
> > >
> > > Return -EPROBE_DEFER to try again later automatically (which is
> > > what the local comments already say we should do anyway).
> >
> > I want to make sure this is not papering over some other issue. Can you
> > post the final topology when this works (cxl list -BPET)? My working
> > theory is that you have 2 devices that share an intermediate port.
> > Otherwise, I am having a hard time understanding why the
> > cxl_bus_rescan() in cxl_acpi_probe() does not obviate the explicit
> > EPROBE_DEFER.
> >
just reporting back with a fully functional layout - they do not appear to
share an intermediate port, unless you consider the root a shared port.
I see your concern about this papering over another issue, but it's not
clear what to look for or how to look for it at this point.
For what it's worth - another group observed the same issue with different
hardware and produced the same patch.
"ports:root0":[
{
"port":"port1",
"host":"pci0000:e0",
"depth":1,
"decoders_committed":1,
"nr_dports":4,
"dports":[
{
"dport":"0000:e0:07.2",
"alias":"device:16",
"id":114
},
{
"dport":"0000:e0:01.1",
"alias":"device:02",
"id":0
},
{
"dport":"0000:e0:01.3",
"alias":"device:05",
"id":2
},
{
"dport":"0000:e0:07.1",
"alias":"device:0d",
"id":113
}
],
"endpoints:port1":[
{
"endpoint":"endpoint5",
"host":"mem0",
"parent_dport":"0000:e0:01.1",
"depth":2,
"decoders_committed":1
}
]
},
{
"port":"port3",
"host":"pci0000:c0",
"depth":1,
"decoders_committed":2,
"nr_dports":1,
"dports":[
{
"dport":"0000:c0:01.1",
"alias":"device:c3",
"id":0
}
],
"endpoints:port3":[
{
"endpoint":"endpoint6",
"host":"mem1",
"parent_dport":"0000:c0:01.1",
"depth":2,
"decoders_committed":2
}
]
},
]
> > So, devA is dependendent on devB to create a common port, but devA loses
> > that race after cxl_bus_rescan() has already run. Then EBPROBE_DEFER is
> > the right answer to trigger devA to try again.
prev parent reply other threads:[~2024-10-01 15:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-13 18:32 Gregory Price
2024-09-14 4:32 ` Dan Williams
2024-09-18 11:59 ` Gregory Price
2024-10-01 15:20 ` Gregory Price [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=ZvwTKxTc9yDypmkG@PC2K9PVX.TheFacebook.com \
--to=gourry@gourry.net \
--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=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rrichter@amd.com \
--cc=terry.bowman@amd.com \
--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
all inboxes | Powered by JetHome®