7f7b4236f2
Some BIOS-es contain a bug where they add addresses which map to system
RAM in the PCI host bridge window returned by the ACPI _CRS method, see
commit 4dc2287c18 ("x86: avoid E820 regions when allocating address
space").
To work around this bug Linux excludes E820 reserved addresses when
allocating addresses from the PCI host bridge window since 2010.
Recently (2019) some systems have shown-up with E820 reservations which
cover the entire _CRS returned PCI bridge memory window, causing all
attempts to assign memory to PCI BARs which have not been setup by the
BIOS to fail. For example here are the relevant dmesg bits from a
Lenovo IdeaPad 3 15IIL 81WE:
[mem 0x000000004bc50000-0x00000000cfffffff] reserved
pci_bus 0000:00: root bus resource [mem 0x65400000-0xbfffffff window]
The ACPI specifications appear to allow this new behavior:
The relationship between E820 and ACPI _CRS is not really very clear.
ACPI v6.3, sec 15, table 15-374, says AddressRangeReserved means:
This range of addresses is in use or reserved by the system and is
not to be included in the allocatable memory pool of the operating
system's memory manager.
and it may be used when:
The address range is in use by a memory-mapped system device.
Furthermore, sec 15.2 says:
Address ranges defined for baseboard memory-mapped I/O devices, such
as APICs, are returned as reserved.
A PCI host bridge qualifies as a baseboard memory-mapped I/O device,
and its apertures are in use and certainly should not be included in
the general allocatable pool, so the fact that some BIOS-es reports
the PCI aperture as "reserved" in E820 doesn't seem like a BIOS bug.
So it seems that the excluding of E820 reserved addresses is a mistake.
Ideally Linux would fully stop excluding E820 reserved addresses,
but then the old systems this was added for will regress.
Instead keep the old behavior for old systems, while ignoring
the E820 reservations for any systems from now on.
Old systems are defined here as BIOS year < 2018, this was chosen to make
sure that E820 reservations will not be used on the currently affected
systems, while at the same time also taking into account that the systems
for which the E820 checking was originally added may have received BIOS
updates for quite a while (esp. CVE related ones), giving them a more
recent BIOS year then 2010.
BugLink: https://bugzilla.kernel.org/show_bug.cgi?id=206459
BugLink: https://bugzilla.redhat.com/show_bug.cgi?id=1868899
BugLink: https://bugzilla.redhat.com/show_bug.cgi?id=1871793
BugLink: https://bugs.launchpad.net/bugs/1878279
BugLink: https://bugs.launchpad.net/bugs/1931715
BugLink: https://bugs.launchpad.net/bugs/1932069
BugLink: https://bugs.launchpad.net/bugs/1921649
Reviewed-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Acked-by: Bjorn Helgaas <bhelgaas@google.com>
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
73 lines
2.1 KiB
C
73 lines
2.1 KiB
C
// SPDX-License-Identifier: GPL-2.0
|
|
#include <linux/dmi.h>
|
|
#include <linux/ioport.h>
|
|
#include <asm/e820/api.h>
|
|
|
|
static void resource_clip(struct resource *res, resource_size_t start,
|
|
resource_size_t end)
|
|
{
|
|
resource_size_t low = 0, high = 0;
|
|
|
|
if (res->end < start || res->start > end)
|
|
return; /* no conflict */
|
|
|
|
if (res->start < start)
|
|
low = start - res->start;
|
|
|
|
if (res->end > end)
|
|
high = res->end - end;
|
|
|
|
/* Keep the area above or below the conflict, whichever is larger */
|
|
if (low > high)
|
|
res->end = start - 1;
|
|
else
|
|
res->start = end + 1;
|
|
}
|
|
|
|
/*
|
|
* Some BIOS-es contain a bug where they add addresses which map to
|
|
* system RAM in the PCI host bridge window returned by the ACPI _CRS
|
|
* method, see commit 4dc2287c1805 ("x86: avoid E820 regions when
|
|
* allocating address space"). To avoid this Linux by default excludes
|
|
* E820 reservations when allocating addresses since 2010.
|
|
* In 2019 some systems have shown-up with E820 reservations which cover
|
|
* the entire _CRS returned PCI host bridge window, causing all attempts
|
|
* to assign memory to PCI BARs to fail if Linux uses E820 reservations.
|
|
*
|
|
* Ideally Linux would fully stop using E820 reservations, but then
|
|
* the old systems this was added for will regress.
|
|
* Instead keep the old behavior for old systems, while ignoring the
|
|
* E820 reservations for any systems from now on.
|
|
*/
|
|
static void remove_e820_regions(struct resource *avail)
|
|
{
|
|
int i, year = dmi_get_bios_year();
|
|
struct e820_entry *entry;
|
|
|
|
if (year >= 2018)
|
|
return;
|
|
|
|
pr_info_once("PCI: Removing E820 reservations from host bridge windows\n");
|
|
|
|
for (i = 0; i < e820_table->nr_entries; i++) {
|
|
entry = &e820_table->entries[i];
|
|
|
|
resource_clip(avail, entry->addr,
|
|
entry->addr + entry->size - 1);
|
|
}
|
|
}
|
|
|
|
void arch_remove_reservations(struct resource *avail)
|
|
{
|
|
/*
|
|
* Trim out BIOS area (high 2MB) and E820 regions. We do not remove
|
|
* the low 1MB unconditionally, as this area is needed for some ISA
|
|
* cards requiring a memory range, e.g. the i82365 PCMCIA controller.
|
|
*/
|
|
if (avail->flags & IORESOURCE_MEM) {
|
|
resource_clip(avail, BIOS_ROM_BASE, BIOS_ROM_END);
|
|
|
|
remove_e820_regions(avail);
|
|
}
|
|
}
|