From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Brian Bloniarz <phunge0@hotmail.com>,
Charles Butterfield <charles.butterfield@nextcentury.com>,
Denys Vlasenko <dvlasenk@redhat.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Stefan Becker <chemobejk@gmail.com>,
"H. Peter Anvin" <hpa@zytor.com>, Yinghai Lu <yinghai@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>,
stable@kernel.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v2 0/4] PCI: allocate space top-down, not bottom-up
Date: Fri, 24 Sep 2010 16:41:39 -0600 [thread overview]
Message-ID: <201009241641.40867.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <20100917223109.24687.17697.stgit@bob.kio>
Added cc: stable@kernel.org
See:
https://patchwork.kernel.org/patch/189182/
https://patchwork.kernel.org/patch/189232/
https://patchwork.kernel.org/patch/189242/
https://patchwork.kernel.org/patch/189252/
On Friday, September 17, 2010 04:32:06 pm Bjorn Helgaas wrote:
> When we move PCI devices, we currently allocate space bottom-up, i.e., we look
> at PCI bus resources in the order we found them, we look at gaps between child
> resources bottom-up, and we align the new space at the bottom of an available
> region.
>
> On x86, we move PCI devices more than we used to because we now pay attention
> to the PCI host bridge windows from ACPI. For example, when we find a device
> that's outside all the known host bridge windows, we try to move it into a
> window, and we look for space starting at the bottom.
>
> Windows does similar device moves, but it looks for space top-down rather than
> bottom-up. Since most machines are better-tested with Windows than Linux, this
> difference means that Linux is more likely to trip over BIOS bugs in the PCI
> host bridge window descriptions than Windows is.
>
> We've had several reports of Dell machines where the BIOS leaves the AHCI
> controller outside the host bridge windows (BIOS bug #1), *and* the lowest
> host bridge window includes an area that doesn't actually reach PCI (BIOS
> bug #2). The result is that Windows (which moves AHCI to the top of a window)
> works fine, while Linux (which moves AHCI to the bottom, buggy, area) doesn't
> work.
>
> These patches change Linux to allocate space more like Windows does:
>
> 1) The x86 pcibios_align_resource() will choose space from the
> end of an available area, not the beginning.
>
> 2) In the generic allocate_resource() path, we'll look for space
> between existing children from the top, not from the bottom.
>
> 3) When pci_bus_alloc_resource() looks for available space, it
> will start from the highest window, not the first one we found.
>
> This series fixes a 2.6.34 regression that prevents many Dell Precision
> workstations from booting:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=16228
>
> Changes from v1 to v2:
> - Moved check for allocating before the available area from
> pcibios_align_resource() to find_resource(). Better to do it
> after the alignment callback is done, and make it generic.
> - Fixed pcibios_align_resource() alignment. If we start from the
> end of the available area, we must align *downward*, not upward.
> - Fixed pcibios_align_resource() ISA alias avoidance. Again, since
> the starting point is the end of the area, we must align downward
> when we avoid aliased areas.
>
> ---
>
> Bjorn Helgaas (4):
> resources: ensure alignment callback doesn't allocate below available start
> x86/PCI: allocate space from the end of a region, not the beginning
> resources: allocate space within a region from the top down
> PCI: allocate bus resources from the top down
>
>
> arch/x86/pci/i386.c | 18 ++++++++++++-----
> drivers/pci/bus.c | 53 ++++++++++++++++++++++++++++++++++++++++++++++-----
> kernel/resource.c | 50 +++++++++++++++++++++++++++++++-----------------
> 3 files changed, 92 insertions(+), 29 deletions(-)
>
next prev parent reply other threads:[~2010-09-24 22:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-17 22:32 Bjorn Helgaas
2010-09-17 22:32 ` [PATCH v2 1/4] resources: ensure alignment callback doesn't allocate below available start Bjorn Helgaas
2010-09-24 17:07 ` Jesse Barnes
2010-09-24 18:15 ` Linus Torvalds
2010-09-24 18:27 ` Jesse Barnes
2010-09-17 22:32 ` [PATCH v2 2/4] x86/PCI: allocate space from the end of a region, not the beginning Bjorn Helgaas
2010-09-17 22:32 ` [PATCH v2 3/4] resources: allocate space within a region from the top down Bjorn Helgaas
2010-09-17 22:32 ` [PATCH v2 4/4] PCI: allocate bus resources " Bjorn Helgaas
2010-09-17 23:46 ` [PATCH v2 0/4] PCI: allocate space top-down, not bottom-up H. Peter Anvin
2010-09-24 22:41 ` Bjorn Helgaas [this message]
2010-09-24 23:40 ` [stable] " Greg KH
2010-09-25 0:52 ` Jesse Barnes
2010-09-25 16:30 ` Bjorn Helgaas
2010-09-25 17:29 ` Greg KH
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=201009241641.40867.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=akpm@linux-foundation.org \
--cc=charles.butterfield@nextcentury.com \
--cc=chemobejk@gmail.com \
--cc=dvlasenk@redhat.com \
--cc=hpa@zytor.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=phunge0@hotmail.com \
--cc=stable@kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=yinghai@kernel.org \
/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
all inboxes | Powered by JetHome®