From: Bjorn Helgaas <helgaas@kernel.org>
To: Szymon Durawa <szymon.durawa@linux.intel.com>
Cc: nirmal.patel@linux.intel.com, djbw@kernel.org,
linux-pci@vger.kernel.org, lukas@wunner.de
Subject: Re: [PATCH v7 8/8] PCI: vmd: Add workaround for bus number hardwired to fixed non-zero value
Date: Thu, 3 Sep 2026 15:58:40 -0500 [thread overview]
Message-ID: <20260903205840.GA2245335@bhelgaas> (raw)
In-Reply-To: <20260902175846.3497854-9-szymon.durawa@linux.intel.com>
On Wed, Sep 02, 2026 at 05:58:44PM +0000, Szymon Durawa wrote:
> The VMD BUS1 root bus number is fixed in hardware to 0x80. It marks bridge
> invalid configuration when detecting a non-zero (0x80) the VMD BUS1 root
> bus number.
Add blank line between paragraphs. I can't quite parse that second
sentence. I don't know who is marking bridge configuration as
invalid.
> Thus root bus number is deconfigured in the first pass of pci_scan_bridge()
> to be re-assigned to 0x0 in the second pass. As a result no subordinate bus
> number behind VMD BUS1 is found.
>
> To avoid bus number reconfiguration, BUS1 number has to be the same
> as BUS1 primary number.
>
> Log snippet without workaround:
>
> [ 3.752507] vmd 0000:00:0e.0: PCI host bridge to bus 10000:e1
You're adding support for a second root bus. So I assume there are
two "PCI host bridge to bus 10000:XX" lines, and it would help
understand this if you included both.
> [ 3.752510] pci_bus 10000:e1: busn_res: can not insert [bus e1-ff] under domain [bus 00-ff] (conflicts with (null) [bus e0-f0])
We should fix whatever results in the "(null)" part here so the
message is more meaningful.
> [ 3.752515] pci_bus 10000:e1: root bus resource [bus f1-ff]
> [ 3.752517] pci_bus 10000:e1: root bus resource [mem 0x8c800000-0x8cffffff]
> [ 3.752519] pci_bus 10000:e1: root bus resource [mem 0x701b802000-0x701bffffff 64bit]
> [ 3.752523] pci_bus 10000:e1: scanning bus
> [ 3.752732] pci (null): Looking for ACPI companion (address 0x80e0ffff)
> [ 3.752745] pci 10000:e1:1c.0: [8086:7f38] type 01 class 0x060400 PCIe Root Port
> [ 3.752779] pci 10000:e1:1c.0: PCI bridge to [bus f1]
> [ 3.752861] pci 10000:e1:1c.0: PME# supported from D0 D3hot D3cold
> [ 3.752864] pci 10000:e1:1c.0: PME# disabled
> [ 3.752909] pci 10000:e1:1c.0: PTM enabled (root), 4ns granularity
> [ 3.752981] pci 10000:e1:1c.0: vgaarb: pci_notify
> [ 3.752987] pci_bus 10000:e1: fixups for bus
> [ 3.752992] pci 10000:e1:1c.0: scanning [bus f1-f1] behind bridge, pass 0
> [ 3.752993] pci 10000:e1:1c.0: primary 80, bus->number e1.
> [ 3.752994] pci 10000:e1:1c.0: bridge configuration invalid ([bus f1-f1]), reconfiguring
> [ 3.753003] pci 10000:e1:1c.0: scanning [bus 00-00] behind bridge, pass 1
> [ 3.753004] pci 10000:e1:1c.0: primary 00, bus->number e1.
Remove timestamps (unless they are telling us something useful) and
indent the quoted log two spaces.
Also remove the unrelated log messages. I don't think the mem
windows, scanning, ACPI companion, Root Port, PME#, PTM, vgaarb stuff
is relevant.
A few nits below.
> Suggested-by: Nirmal Patel <nirmal.patel@linux.intel.com>
> Signed-off-by: Szymon Durawa <szymon.durawa@linux.intel.com>
> ---
> drivers/pci/controller/vmd.c | 66 ++++++++++++++++++++++++++++++++----
> 1 file changed, 60 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/pci/controller/vmd.c b/drivers/pci/controller/vmd.c
> index 7e76ef3d7ec8..f4c6a16e8473 100644
> --- a/drivers/pci/controller/vmd.c
> +++ b/drivers/pci/controller/vmd.c
> @@ -467,10 +467,23 @@ static unsigned int vmd_bus_to_ecam(struct vmd_dev *vmd, unsigned int busnr)
> static void __iomem *vmd_cfg_addr(struct vmd_dev *vmd, struct pci_bus *bus,
> unsigned int devfn, int reg, int len)
> {
> + unsigned char bus_number;
> unsigned int busnr_ecam;
> u32 offset;
>
> - busnr_ecam = vmd_bus_to_ecam(vmd, bus->number);
> + /*
> + * Remap ONLY the virtual BUS1 root bus number (0x80) to its physical
> + * CFGBAR start aperture (0xE1). Downstream subordinate buses behind
> + * the root port are assigned physical numbers (0xF1..0xFF per
> + * VMD_BUSRANGE1) and must NOT be remapped, otherwise child endpoint
> + * accesses would target the root port rather than their own ECAM space.
> + */
> + if (vmd->bus1_rootbus && bus->number == VMD_PRIMARY_BUS1)
> + bus_number = vmd->busn_start[VMD_BUS_1];
> + else
> + bus_number = bus->number;
> +
> + busnr_ecam = vmd_bus_to_ecam(vmd, bus_number);
> offset = PCIE_ECAM_OFFSET(busnr_ecam, devfn, reg);
>
> if (offset + len >= resource_size(&vmd->dev->resource[VMD_CFGBAR]))
> @@ -550,18 +563,39 @@ static struct pci_ops vmd_ops = {
> static struct acpi_device *vmd_acpi_find_companion(struct pci_dev *pci_dev)
> {
> struct pci_host_bridge *bridge;
> - u32 busnr, addr;
> + struct vmd_dev *vmd;
> + u32 addr;
> + int busnr;
> + u8 pci_bus_number;
> + u8 bridge_bus_number;
>
> if (pci_dev->bus->ops != &vmd_ops)
> return NULL;
>
> + vmd = vmd_from_bus(pci_dev->bus);
> bridge = pci_find_host_bridge(pci_dev->bus);
> - busnr = pci_dev->bus->number - bridge->bus->number;
> + pci_bus_number = pci_dev->bus->number;
> + bridge_bus_number = bridge->bus->number;
> +
> + /*
> + * BUS1 is registered with logical root number 0x80. For ACPI companion
> + * matching, map only the logical root bus (0x80) to the physical
> + * BUS1 start base (0xE1). Downstream child buses (0xF1..0xFF) already
> + * reflect their physical bus numbers and must remain untranslated to
> + * produce the correct relative depth against bridge_bus_number.
> + */
> + if (vmd->bus1_rootbus && bridge->bus == vmd->bus[VMD_BUS_1]) {
> + bridge_bus_number = vmd->busn_start[VMD_BUS_1];
> + if (pci_bus_number == VMD_PRIMARY_BUS1)
> + pci_bus_number = vmd->busn_start[VMD_BUS_1];
> + }
> +
> + busnr = pci_bus_number - bridge_bus_number;
Need a blank line here to follow existing style.
> /*
> * The address computation below is only applicable to relative bus
> * numbers below 32.
> */
> - if (busnr > 31)
> + if (busnr < 0 || busnr > 31)
> return NULL;
>
> addr = (busnr << 24) | ((u32)pci_dev->devfn << 16) | 0x8000FFFFU;
> @@ -1186,6 +1220,7 @@ static int vmd_create_bus(struct vmd_dev *vmd, enum vmd_rootbus bus_number,
> struct pci_sysdata *sd, resource_size_t *offset,
> u8 primary)
> {
> + u8 root_busnr;
> u8 cfgbar = bus_number * 3;
> u8 membar1 = cfgbar + 1;
> u8 membar2 = cfgbar + 2;
> @@ -1198,8 +1233,27 @@ static int vmd_create_bus(struct vmd_dev *vmd, enum vmd_rootbus bus_number,
> pci_add_resource_offset(&resources, &vmd->resources[membar2],
> offset[1]);
>
> - vmd_bus = pci_create_root_bus(&vmd->dev->dev,
> - vmd->busn_start[bus_number], &vmd_ops, sd,
> + /*
> + * Register BUS1 with its logical root number (0x80) up front so PCI core
> + * bridge scanning does not see a post-registration bus-number mutation.
> + *
> + * This is a workaround for pci_scan_bridge_extend() code.
> + * It marks bridge invalid configuration when detecting a
> + * non-zero (0x80) the VMD BUS1 root bus number. Thus Primary Bus Number
> + * of Root Ports on BUS1 is deconfigured in the first pass of
> + * pci_scan_bridge() to be re-assigned to 0x0 in the second pass.
> + * As a result no subordinate bus number behind VMD BUS1 is found.
> + * Workaround: VMD_BUS_1 bus number shall be set to VMD_PRIMARY_BUS1 so it has
> + * the same value as vmd->bus[VMD_BUS_1]->primary, it will bypass bus number
> + * reconfiguration.
Make sure your comments all fit in 80 columns.
Add blank lines between paragraphs.
> + */
> +
Don't need a blank line here.
> + if (bus_number == VMD_BUS_1 && vmd->bus1_rootbus)
> + root_busnr = VMD_PRIMARY_BUS1;
> + else
> + root_busnr = vmd->busn_start[bus_number];
> +
> + vmd_bus = pci_create_root_bus(&vmd->dev->dev, root_busnr, &vmd_ops, sd,
> &resources);
>
> if (!vmd_bus) {
> --
> 2.43.0
>
prev parent reply other threads:[~2026-09-03 20:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 17:58 [PATCH v7 0/8] PCI: vmd: Add support for second rootbus under VMD Szymon Durawa
2026-09-02 17:58 ` [PATCH v7 1/8] PCI: vmd: Add vmd_bus_enumeration() helper function Szymon Durawa
2026-09-02 17:58 ` [PATCH v7 2/8] PCI: vmd: Add vmd_configure_cfgbar() " Szymon Durawa
2026-09-02 17:58 ` [PATCH v7 3/8] PCI: vmd: Add vmd_configure_membar() and vmd_configure_membar1_membar2() Szymon Durawa
2026-09-02 17:58 ` [PATCH v7 4/8] PCI: vmd: Add vmd_create_bus() Szymon Durawa
2026-09-02 17:58 ` [PATCH v7 5/8] PCI: vmd: Replace hardcoded values with enum and defines Szymon Durawa
2026-09-02 17:58 ` [PATCH v7 6/8] PCI: vmd: Convert bus and busn_start to an array Szymon Durawa
2026-09-02 17:58 ` [PATCH v7 7/8] PCI: vmd: Add support for second rootbus under VMD Szymon Durawa
2026-09-02 17:58 ` [PATCH v7 8/8] PCI: vmd: Add workaround for bus number hardwired to fixed non-zero value Szymon Durawa
2026-09-03 20:58 ` Bjorn Helgaas [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=20260903205840.GA2245335@bhelgaas \
--to=helgaas@kernel.org \
--cc=djbw@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=nirmal.patel@linux.intel.com \
--cc=szymon.durawa@linux.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