From: Bjorn Helgaas <helgaas@kernel.org>
To: Kai-Heng Feng <kai.heng.feng@canonical.com>
Cc: bhelgaas@google.com, Guenter Roeck <linux@roeck-us.net>,
"open list:PCI SUBSYSTEM" <linux-pci@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] PCI: Reinstate "PCI: Coalesce host bridge contiguous apertures"
Date: Wed, 29 Sep 2021 16:25:44 -0500 [thread overview]
Message-ID: <20210929212544.GA808906@bhelgaas> (raw)
In-Reply-To: <20210713125007.1260304-1-kai.heng.feng@canonical.com>
On Tue, Jul 13, 2021 at 08:50:07PM +0800, Kai-Heng Feng wrote:
> Built-in graphics on HP EliteDesk 805 G6 doesn't work because graphics
> can't get the BAR it needs:
> pci_bus 0000:00: root bus resource [mem 0x10020200000-0x100303fffff window]
> pci_bus 0000:00: root bus resource [mem 0x10030400000-0x100401fffff window]
>
> pci 0000:00:08.1: bridge window [mem 0xd2000000-0xd23fffff]
> pci 0000:00:08.1: bridge window [mem 0x10030000000-0x100401fffff 64bit pref]
> pci 0000:00:08.1: can't claim BAR 15 [mem 0x10030000000-0x100401fffff 64bit pref]: no compatible bridge window
> pci 0000:00:08.1: [mem 0x10030000000-0x100401fffff 64bit pref] clipped to [mem 0x10030000000-0x100303fffff 64bit pref]
> pci 0000:00:08.1: bridge window [mem 0x10030000000-0x100303fffff 64bit pref]
> pci 0000:07:00.0: can't claim BAR 0 [mem 0x10030000000-0x1003fffffff 64bit pref]: no compatible bridge window
> pci 0000:07:00.0: can't claim BAR 2 [mem 0x10040000000-0x100401fffff 64bit pref]: no compatible bridge window
>
> However, the root bus has two contiguous apertures that can contain the
> child resource requested.
>
> Coalesce contiguous apertures so we can allocate from the entire contiguous
> region.
>
> This is the second take of commit 65db04053efe ("PCI: Coalesce host
> bridge contiguous apertures"). The original approach sorts the apertures
> by address, but that makes NVMe stop working on QEMU ppc:sam460ex:
> PCI host bridge to bus 0002:00
> pci_bus 0002:00: root bus resource [io 0x0000-0xffff]
> pci_bus 0002:00: root bus resource [mem 0xd80000000-0xdffffffff] (bus address [0x80000000-0xffffffff])
> pci_bus 0002:00: root bus resource [mem 0xc0ee00000-0xc0eefffff] (bus address [0x00000000-0x000fffff])
>
> After the offending commit:
> PCI host bridge to bus 0002:00
> pci_bus 0002:00: root bus resource [io 0x0000-0xffff]
> pci_bus 0002:00: root bus resource [mem 0xc0ee00000-0xc0eefffff] (bus address [0x00000000-0x000fffff])
> pci_bus 0002:00: root bus resource [mem 0xd80000000-0xdffffffff] (bus address [0x80000000-0xffffffff])
>
> Since the apertures on HP EliteDesk 805 G6 are already in ascending
> order, doing a precautious sorting is not necessary.
>
> Remove the sorting part to avoid the regression on ppc:sam460ex.
>
> Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=212013
> Cc: Guenter Roeck <linux@roeck-us.net>
> Suggested-by: Bjorn Helgaas <bhelgaas@google.com>
> Signed-off-by: Kai-Heng Feng <kai.heng.feng@canonical.com>
Applied to pci/resource for v5.16, thanks!
> ---
> v2:
> - Bring back the original commit message.
>
> drivers/pci/probe.c | 31 +++++++++++++++++++++++++++----
> 1 file changed, 27 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/pci/probe.c b/drivers/pci/probe.c
> index 79177ac37880..5de157600466 100644
> --- a/drivers/pci/probe.c
> +++ b/drivers/pci/probe.c
> @@ -877,11 +877,11 @@ static void pci_set_bus_msi_domain(struct pci_bus *bus)
> static int pci_register_host_bridge(struct pci_host_bridge *bridge)
> {
> struct device *parent = bridge->dev.parent;
> - struct resource_entry *window, *n;
> + struct resource_entry *window, *next, *n;
> struct pci_bus *bus, *b;
> - resource_size_t offset;
> + resource_size_t offset, next_offset;
> LIST_HEAD(resources);
> - struct resource *res;
> + struct resource *res, *next_res;
> char addr[64], *fmt;
> const char *name;
> int err;
> @@ -961,11 +961,34 @@ static int pci_register_host_bridge(struct pci_host_bridge *bridge)
> if (nr_node_ids > 1 && pcibus_to_node(bus) == NUMA_NO_NODE)
> dev_warn(&bus->dev, "Unknown NUMA node; performance will be reduced\n");
>
> + /* Coalesce contiguous windows */
> + resource_list_for_each_entry_safe(window, n, &resources) {
> + if (list_is_last(&window->node, &resources))
> + break;
> +
> + next = list_next_entry(window, node);
> + offset = window->offset;
> + res = window->res;
> + next_offset = next->offset;
> + next_res = next->res;
> +
> + if (res->flags != next_res->flags || offset != next_offset)
> + continue;
> +
> + if (res->end + 1 == next_res->start) {
> + next_res->start = res->start;
> + res->flags = res->start = res->end = 0;
> + }
> + }
> +
> /* Add initial resources to the bus */
> resource_list_for_each_entry_safe(window, n, &resources) {
> - list_move_tail(&window->node, &bridge->windows);
> offset = window->offset;
> res = window->res;
> + if (!res->end)
> + continue;
> +
> + list_move_tail(&window->node, &bridge->windows);
>
> if (res->flags & IORESOURCE_BUS)
> pci_bus_insert_busn_res(bus, bus->number, res->end);
> --
> 2.31.1
>
next prev parent reply other threads:[~2021-09-29 21:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-13 7:57 [PATCH 1/1] PCI: Coalesce host bridge contiguous apertures without sorting Kai-Heng Feng
2021-07-13 8:45 ` Guenter Roeck
2021-07-13 8:49 ` Kai-Heng Feng
2021-07-13 9:06 ` Guenter Roeck
2021-07-13 12:50 ` [PATCH v2] PCI: Reinstate "PCI: Coalesce host bridge contiguous apertures" Kai-Heng Feng
2021-09-29 21:25 ` Bjorn Helgaas [this message]
2021-11-17 14:12 ` Johannes Berg
2022-07-13 9:36 ` Geert Uytterhoeven
2021-08-09 4:24 ` [PATCH] PCI/portdrv: Disallow runtime suspend when waekup is required but PME service isn't supported Kai-Heng Feng
2021-08-09 9:47 ` Lukas Wunner
2021-08-09 10:40 ` Kai-Heng Feng
2021-08-09 15:00 ` Lukas Wunner
2021-08-10 15:37 ` Kai-Heng Feng
2021-08-10 16:21 ` Lukas Wunner
2021-08-11 5:06 ` Kai-Heng Feng
2021-08-11 7:11 ` Lukas Wunner
2021-08-12 5:20 ` Kai-Heng Feng
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=20210929212544.GA808906@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=kai.heng.feng@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux@roeck-us.net \
/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).