From: Logan Gunthorpe <logang@deltatee.com>
To: Bjorn Helgaas <helgaas@kernel.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Nicholas Johnson <nicholas.johnson-opensource@outlook.com.au>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linux-pci@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: [PATCH 2/2] PCI: Skip resource distribution when no hotplug bridges
Date: Mon, 24 Jun 2019 10:26:08 -0600 [thread overview]
Message-ID: <13911af4-66f5-ece8-378b-6af8eba98381@deltatee.com> (raw)
In-Reply-To: <20190622210310.180905-3-helgaas@kernel.org>
On 2019-06-22 3:03 p.m., Bjorn Helgaas wrote:
> From: Bjorn Helgaas <bhelgaas@google.com>
>
> If "hotplug_bridges == 0", "!dev->is_hotplug_bridge" is always true, so the
> loop that divides the remaining resources among hotplug-capable bridges
> does nothing.
>
> Check for "hotplug_bridges == 0" earlier, so we don't even have to compute
> the amount of remaining resources. No functional change intended.
Makes sense.
Reviewed-by: Logan Gunthorpe <logang@deltatee.com>
> ---
>
> I'm pretty sure this patch preserves the previous behavior of
> pci_bus_distribute_available_resources(), but I'm not sure that
> behavior is what we want.
>
> For example, in the following topology, when we process bus 10, we
> find two non-hotplug bridges and no hotplug bridges, so IIUC we return
> without distributing any resources to them. But I would think we
> should try to give 10:1c.0 more space if possible because it has a
> hotplug bridge below it.
>
> 00:1c.0: hotplug bridge to [bus 10-2f]
> 10:1c.0: non-hotplug bridge to [bus 11-2e]
> 11:00.0: hotplug bridge to [bus 12-2e]
> 10:1c.1: non-hotplug bridge to [bus 2f]
> ---
> drivers/pci/setup-bus.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/pci/setup-bus.c b/drivers/pci/setup-bus.c
> index af28af898e42..04adeebe8866 100644
> --- a/drivers/pci/setup-bus.c
> +++ b/drivers/pci/setup-bus.c
> @@ -1887,6 +1887,9 @@ static void pci_bus_distribute_available_resources(struct pci_bus *bus,
> return;
> }
>
> + if (hotplug_bridges == 0)
> + return;
> +
> /*
> * Calculate the total amount of extra resource space we can
> * pass to bridges below this one. This is basically the
> @@ -1936,8 +1939,6 @@ static void pci_bus_distribute_available_resources(struct pci_bus *bus,
> * Distribute available extra resources equally between
> * hotplug-capable downstream ports taking alignment into
> * account.
> - *
> - * Here hotplug_bridges is always != 0.
> */
> align = pci_resource_alignment(bridge, io_res);
> io = div64_ul(available_io, hotplug_bridges);
>
prev parent reply other threads:[~2019-06-24 16:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-22 21:03 [PATCH 0/2] PCI: Simplify pci_bus_distribute_available_resources() Bjorn Helgaas
2019-06-22 21:03 ` [PATCH 1/2] " Bjorn Helgaas
2019-06-24 11:09 ` Mika Westerberg
2019-06-24 16:21 ` Logan Gunthorpe
2019-06-22 21:03 ` [PATCH 2/2] PCI: Skip resource distribution when no hotplug bridges Bjorn Helgaas
2019-06-24 11:24 ` Mika Westerberg
2019-06-24 23:45 ` Benjamin Herrenschmidt
2019-06-25 10:05 ` Mika Westerberg
2019-06-25 11:48 ` Benjamin Herrenschmidt
2019-06-25 12:04 ` Mika Westerberg
2019-06-25 12:23 ` Benjamin Herrenschmidt
2019-06-25 12:43 ` Mika Westerberg
2019-06-25 23:22 ` Benjamin Herrenschmidt
2019-06-26 17:35 ` Bjorn Helgaas
2019-06-26 22:35 ` Benjamin Herrenschmidt
2019-06-24 16:26 ` Logan Gunthorpe [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=13911af4-66f5-ece8-378b-6af8eba98381@deltatee.com \
--to=logang@deltatee.com \
--cc=benh@kernel.crashing.org \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=nicholas.johnson-opensource@outlook.com.au \
/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;
as well as URLs for NNTP newsgroup(s).