From: "Dan Williams (nvidia)" <djbw@kernel.org>
To: Chen Pei <cp0613@linux.alibaba.com>, icheng@nvidia.com
Cc: alison.schofield@intel.com, cp0613@linux.alibaba.com,
dave.jiang@intel.com, dave@stgolabs.net, djbw@kernel.org,
guoren@kernel.org, ira.weiny@intel.com, jic23@kernel.org,
linux-cxl@vger.kernel.org, linux-kernel@vger.kernel.org,
vishal.l.verma@intel.com
Subject: Re: [PATCH] cxl/acpi: Defer probe when ACPI0016 PCI root bridge is not ready
Date: Fri, 15 May 2026 12:24:50 -0700 [thread overview]
Message-ID: <6a07730211b81_a6174100c8@djbw-dev.notmuch> (raw)
In-Reply-To: <20260515134652.15486-1-cp0613@linux.alibaba.com>
Chen Pei wrote:
> On Thu, 14 May 2026 15:31:11 +0800, Richard Cheng wrote:
>
> > > On some platforms (e.g., RISC-V and ARM64) that use the generic
> > > pci_acpi_scan_root() implementation, cxl_acpi_probe may run before
> > > acpi_pci_root driver has bound to ACPI0016 (CXL host bridge) devices.
> > > In this case, acpi_pci_find_root() returns NULL, causing
> > > to_cxl_host_bridge() to skip the device silently. This results in
> > > incomplete CXL port enumeration on first boot.
> > >
> > > Fix this by detecting the case where an ACPI0016 device exists but its
> > > PCI root bridge is not yet ready, and returning -EPROBE_DEFER to trigger
> > > a deferred probe retry.
> > >
> > > Signed-off-by: Chen Pei <cp0613@linux.alibaba.com>
> > > ---
> > > drivers/cxl/acpi.c | 26 ++++++++++++++++++++++++--
> > > 1 file changed, 24 insertions(+), 2 deletions(-)
> > >
> >
> > Hi Chen Pei,
> >
> > Thanks for the patch.
> > I have a few questions and suggestions regarding to your changes.
> >
> > First of all I would like in which scenario did you encounter the bug?
> > Any specific CONFIG options and the devices ? what's the error log ?
> >
> > It would be nice if you can attach it for us.
>
> Hi Richard,
>
> Thanks for the review.
>
> I'm currently working on bringing up CXL support on the RISC-V QEMU
> virt platform with ACPI (EDK2 UEFI firmware). This is still in the
> early debugging/enabling stage.
>
> During testing, I found that cxl_acpi (ACPI0017) probes before
> acpi_pci_root has bound to the ACPI0016 (CXL host bridge) device.
> RISC-V uses the generic pci_acpi_scan_root() implementation, where
> the probe ordering of acpi_pci_root relative to cxl_acpi is not
> guaranteed.
>
> On x86, acpi_pci_root uses subsys_initcall and binds very early,
> so this race does not manifest there.
If the platform is defined to defer PCI root scans then this dependency
must be declared. Specifically firmware needs to tell Linux about the
dependency given it does not order PCI enumeration before ACPI0017
enumeration by default. Something like:
Device (CXLM) { // ACPI0017
Name (_HID, "ACPI0017")
Name (_DEP, Package () {
\_SB.CXL0, // ACPI0016 host bridge
\_SB.CXL1,
})
}
...in the firmware, and then:
acpi_dev_clear_dependencies()
...for each acpi_pci_root_add().
Then ACPI0017 will naturally await all of the ACPI0016 devices that the
firmware knows about.
Otherwise EPROBE_DEFER and scanning for ACPI0016 attachment is
introducing a mess that _DEP was meant to solve.
next prev parent reply other threads:[~2026-05-15 19:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-14 2:32 [PATCH] cxl/acpi: Defer probe when ACPI0016 PCI root bridge is not ready Chen Pei
2026-05-14 7:31 ` Richard Cheng
2026-05-15 13:46 ` Chen Pei
2026-05-15 19:24 ` Dan Williams (nvidia) [this message]
2026-05-14 17:10 ` Dave Jiang
2026-05-15 13:53 ` Chen Pei
2026-05-14 17:19 ` Alison Schofield
2026-05-15 13:56 ` Chen Pei
2026-05-15 15:38 ` Dave Jiang
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=6a07730211b81_a6174100c8@djbw-dev.notmuch \
--to=djbw@kernel.org \
--cc=alison.schofield@intel.com \
--cc=cp0613@linux.alibaba.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=guoren@kernel.org \
--cc=icheng@nvidia.com \
--cc=ira.weiny@intel.com \
--cc=jic23@kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@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