From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Lukas Wunner <lukas@wunner.de>,
"Chris Chiu" <chris.chiu@canonical.com>,
<linux-pci@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] Revert "Revert "PCI: Distribute available resources for root buses, too""
Date: Wed, 16 Nov 2022 09:47:56 +0000 [thread overview]
Message-ID: <20221116094756.0000020e@Huawei.com> (raw)
In-Reply-To: <20221114115953.40236-2-mika.westerberg@linux.intel.com>
On Mon, 14 Nov 2022 13:59:53 +0200
Mika Westerberg <mika.westerberg@linux.intel.com> wrote:
> This reverts commit 5632e2beaf9d5dda694c0572684dea783d8a9492.
>
> Now that pci_bridge_distribute_available_resources() takes multifunction
> devices int account we can revert this revert to fix the original issue.
into account
Looks fine to me, but I never really figured out the original logic
properly so will leave it to others to give tags on this one.
>
> Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
> ---
> drivers/pci/setup-bus.c | 62 ++++++++++++++++++++++++++++++++++++++++-
> 1 file changed, 61 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/pci/setup-bus.c b/drivers/pci/setup-bus.c
> index f3f39aa82dda..dfa490da728d 100644
> --- a/drivers/pci/setup-bus.c
> +++ b/drivers/pci/setup-bus.c
> @@ -1768,7 +1768,10 @@ static void adjust_bridge_window(struct pci_dev *bridge, struct resource *res,
> }
>
> res->end = res->start + new_size - 1;
> - remove_from_list(add_list, res);
> +
> + /* If the resource is part of the add_list remove it now */
> + if (add_list)
> + remove_from_list(add_list, res);
> }
>
> static void pci_bus_distribute_available_resources(struct pci_bus *bus,
> @@ -1971,6 +1974,8 @@ static void pci_bridge_distribute_available_resources(struct pci_dev *bridge,
> if (!bridge->is_hotplug_bridge)
> return;
>
> + pci_dbg(bridge, "distributing available resources\n");
> +
> /* Take the initial extra resources from the hotplug port */
> available_io = bridge->resource[PCI_BRIDGE_IO_WINDOW];
> available_mmio = bridge->resource[PCI_BRIDGE_MEM_WINDOW];
> @@ -1982,6 +1987,59 @@ static void pci_bridge_distribute_available_resources(struct pci_dev *bridge,
> available_mmio_pref);
> }
>
> +static bool pci_bridge_resources_not_assigned(struct pci_dev *dev)
> +{
> + const struct resource *r;
> +
> + /*
> + * Check the child device's resources and if they are not yet
> + * assigned it means we are configuring them (not the boot
> + * firmware) so we should be able to extend the upstream
> + * bridge's (that's the hotplug downstream PCIe port) resources
> + * in the same way we do with the normal hotplug case.
> + */
> + r = &dev->resource[PCI_BRIDGE_IO_WINDOW];
> + if (!r->flags || !(r->flags & IORESOURCE_STARTALIGN))
> + return false;
> + r = &dev->resource[PCI_BRIDGE_MEM_WINDOW];
> + if (!r->flags || !(r->flags & IORESOURCE_STARTALIGN))
> + return false;
> + r = &dev->resource[PCI_BRIDGE_PREF_MEM_WINDOW];
> + if (!r->flags || !(r->flags & IORESOURCE_STARTALIGN))
> + return false;
> +
> + return true;
> +}
> +
> +static void pci_root_bus_distribute_available_resources(struct pci_bus *bus,
> + struct list_head *add_list)
> +{
> + struct pci_dev *dev, *bridge = bus->self;
> +
> + for_each_pci_bridge(dev, bus) {
> + struct pci_bus *b;
> +
> + b = dev->subordinate;
> + if (!b)
> + continue;
> +
> + /*
> + * Need to check "bridge" here too because it is NULL
> + * in case of root bus.
> + */
> + if (bridge && pci_bridge_resources_not_assigned(dev)) {
> + pci_bridge_distribute_available_resources(bridge, add_list);
> + /*
> + * There is only PCIe upstream port on the bus
> + * so we don't need to go futher.
> + */
> + return;
> + }
> +
> + pci_root_bus_distribute_available_resources(b, add_list);
> + }
> +}
> +
> /*
> * First try will not touch PCI bridge res.
> * Second and later try will clear small leaf bridge res.
> @@ -2021,6 +2079,8 @@ void pci_assign_unassigned_root_bus_resources(struct pci_bus *bus)
> */
> __pci_bus_size_bridges(bus, add_list);
>
> + pci_root_bus_distribute_available_resources(bus, add_list);
> +
> /* Depth last, allocate resources and update the hardware. */
> __pci_bus_assign_resources(bus, add_list, &fail_head);
> if (add_list)
next prev parent reply other threads:[~2022-11-16 9:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 11:59 [PATCH v2 1/2] PCI: Take multifunction devices into account when distributing resources Mika Westerberg
2022-11-14 11:59 ` [PATCH v2 2/2] Revert "Revert "PCI: Distribute available resources for root buses, too"" Mika Westerberg
2022-11-16 9:47 ` Jonathan Cameron [this message]
2022-11-14 18:34 ` [PATCH v2 1/2] PCI: Take multifunction devices into account when distributing resources Rafael J. Wysocki
2022-11-16 9:46 ` Jonathan Cameron
2022-11-17 23:10 ` Bjorn Helgaas
2022-11-18 8:57 ` Mika Westerberg
2022-11-18 12:29 ` Bjorn Helgaas
2022-11-21 11:47 ` Mika Westerberg
2022-11-21 22:45 ` Bjorn Helgaas
2022-11-22 6:42 ` Mika Westerberg
2022-11-22 11:45 ` Jonathan Cameron
2022-11-22 12:21 ` Mika Westerberg
2022-11-22 17:26 ` Bjorn Helgaas
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=20221116094756.0000020e@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=chris.chiu@canonical.com \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=mika.westerberg@linux.intel.com \
--cc=rafael.j.wysocki@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 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.