Commit 720a02a5 authored by Bjorn Helgaas's avatar Bjorn Helgaas Committed by Luis Henriques

x86/PCI: Use host bridge _CRS info on systems with >32 bit addressing

commit 3d9fecf6 upstream.

We enable _CRS on all systems from 2008 and later.  On older systems, we
ignore _CRS and assume the whole physical address space (excluding RAM and
other devices) is available for PCI devices, but on systems that support
physical address spaces larger than 4GB, it's doubtful that the area above
4GB is really available for PCI.

After d56dbf5b ("PCI: Allocate 64-bit BARs above 4G when possible"), we
try to use that space above 4GB *first*, so we're more likely to put a
device there.

On Juan's Toshiba Satellite Pro U200, BIOS left the graphics, sound, 1394,
and card reader devices unassigned (but only after Windows had been
booted).  Only the sound device had a 64-bit BAR, so it was the only device
placed above 4GB, and hence the only device that didn't work.

Keep _CRS enabled even on pre-2008 systems if they support physical address
space larger than 4GB.

Fixes: d56dbf5b ("PCI: Allocate 64-bit BARs above 4G when possible")
Reported-and-tested-by: default avatarJuan Dayer <jdayer@outlook.com>
Reported-and-tested-by: default avatarAlan Horsfield <alan@hazelgarth.co.uk>
Link: https://bugzilla.kernel.org/show_bug.cgi?id=99221
Link: https://bugzilla.opensuse.org/show_bug.cgi?id=907092Signed-off-by: default avatarBjorn Helgaas <bhelgaas@google.com>
Signed-off-by: default avatarLuis Henriques <luis.henriques@canonical.com>
parent 10cff415
...@@ -135,8 +135,10 @@ void __init pci_acpi_crs_quirks(void) ...@@ -135,8 +135,10 @@ void __init pci_acpi_crs_quirks(void)
{ {
int year; int year;
if (dmi_get_date(DMI_BIOS_DATE, &year, NULL, NULL) && year < 2008) if (dmi_get_date(DMI_BIOS_DATE, &year, NULL, NULL) && year < 2008) {
if (iomem_resource.end <= 0xffffffff)
pci_use_crs = false; pci_use_crs = false;
}
dmi_check_system(pci_crs_quirks); dmi_check_system(pci_crs_quirks);
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment