[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100223172355.17242.55927.stgit@bob.kio>
Date: Tue, 23 Feb 2010 10:24:15 -0700
From: Bjorn Helgaas <bjorn.helgaas@...com>
To: Jesse Barnes <jbarnes@...tuousgeek.org>
Cc: Matthew Garrett <mjg59@...f.ucam.org>,
Tony Luck <tony.luck@...el.com>, linux-acpi@...r.kernel.org,
linux-pci@...r.kernel.org, Peter Haight <peterh@...ros.com>,
Gary Hade <garyhade@...ibm.com>, linux-kernel@...r.kernel.org,
linuxppc-dev@...abs.org, linux-am33-list@...hat.com,
Yinghai Lu <yinghai@...nel.org>, Ingo Molnar <mingo@...e.hu>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Larry Finger <Larry.Finger@...inger.net>
Subject: [PATCH v5 0/5] PCI: try "pci=use_crs" again
Historically, Linux has assumed a single PCI host bridge, with that bridge
claiming all the address space left after RAM and legacy devices are taken out.
If the system contains multiple host bridges, we can no longer operate under
that assumption. We have to know what parts of the address space are claimed
by each bridge so that when we assign resources to a PCI device, we take them
from a range claimed by the upstream host bridge.
On x86 and ia64, we use ACPI to enumerate all the PCI host bridges in the
system, and part of the host bridge description is the "_CRS" (current resource
settings" property, which lists the address space used by the bridge. On x86,
we currently ignore most of the _CRS information. This patch series changes
this, so we will use _CRS to learn about the host bridge windows.
Since most x86 machines with multiple host bridges are relatively new, this
series only turns this on for machines with BIOS dates of 2008 or newer.
Changes from v4 to v5:
- Add EXPORT_SYMBOL_GPL(pci_bus_resource_n) for module builds.
Changes from v3 to v4:
- Keep the bus->resource[] table to avoid having to change all arches
at once, but reduce it to size 4 (minimum required for P2P & CardBus
bridges).
- Store additional host bridge or subtractive decode windows in a list.
- Add pci_bus_for_each_resource() iterator to hide PCI_BUS_NUM_RESOURCES
and the table/list split. This reduces the size of the main patch.
- Remove tidy-up patches completely; they feel like distractions to this
series.
Changes from v2 to v3:
- Fix alpha, powerpc, and mn10300 references to pci_bus resource table
- Turn on "pci=use_crs" for 2008 and newer, not 2010 and newer
- Remove Toshiba A355 quirk (BIOS date is 2009, so automatically included)
- Remove IBM x3850 and x3950 quirks (BIOS dates in 2008, so automatically
included)
- Leave IBM x3800 quirk (pre-2008 BIOS)
- Use "bool" for pci_use_crs (new to me, but I see akpm suggesting it)
- Reorder so the important patches are first
Changes from v1 to v2:
- Rebase to be6e9f7853e
- Add patch to clean up "disabled window" printk
- Add bugzilla reference comment in use_crs DMI quirk
---
Bjorn Helgaas (5):
PCI: split up pci_read_bridge_bases()
PCI: read bridge windows before filling in subtractive decode resources
PCI: add pci_bus_for_each_resource(), remove direct bus->resource[] refs
PCI: augment bus resource table with a list
x86/PCI: use host bridge _CRS info by default on 2008 and newer machines
Documentation/kernel-parameters.txt | 8 ++-
arch/ia64/include/asm/acpi.h | 1
arch/ia64/pci/pci.c | 17 ++-----
arch/mn10300/unit-asb2305/pci.c | 6 +-
arch/powerpc/kernel/pci-common.c | 11 ++---
arch/powerpc/platforms/fsl_uli1575.c | 12 ++---
arch/x86/include/asm/pci_x86.h | 1
arch/x86/pci/acpi.c | 82 ++++++++++++++++++++--------------
arch/x86/pci/bus_numa.c | 3 +
arch/x86/pci/bus_numa.h | 3 -
arch/x86/pci/common.c | 3 +
drivers/acpi/pci_root.c | 1
drivers/pci/bus.c | 49 +++++++++++++++++++-
drivers/pci/hotplug/shpchp_sysfs.c | 9 +---
drivers/pci/pci.c | 5 +-
drivers/pci/probe.c | 68 ++++++++++++++++++++++------
drivers/pci/setup-bus.c | 10 ++--
drivers/pcmcia/rsrc_nonstatic.c | 3 -
drivers/pcmcia/yenta_socket.c | 5 +-
include/acpi/acpi_drivers.h | 1
include/linux/pci.h | 36 +++++++++++++--
21 files changed, 226 insertions(+), 108 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists