2010-12-17 00:38:51 +07:00
|
|
|
#include <linux/ioport.h>
|
|
|
|
#include <asm/e820.h>
|
|
|
|
|
x86: avoid E820 regions when allocating address space
When we allocate address space, e.g., to assign it to a PCI device, don't
allocate anything mentioned in the BIOS E820 memory map.
On recent machines (2008 and newer), we assign PCI resources from the
windows described by the ACPI PCI host bridge _CRS. On many Dell
machines, these windows overlap some E820 reserved areas, e.g.,
BIOS-e820: 00000000bfe4dc00 - 00000000c0000000 (reserved)
pci_root PNP0A03:00: host bridge window [mem 0xbff00000-0xdfffffff]
If we put devices at 0xbff00000, they don't work, probably because
that's really RAM, not I/O memory. This patch prevents that by removing
the 0xbfe4dc00-0xbfffffff area from the "available" resource.
I'm not very happy with this solution because Windows solves the problem
differently (it seems to ignore E820 reserved areas and it allocates
top-down instead of bottom-up; details at comment 45 of the bugzilla
below). That means we're vulnerable to BIOS defects that Windows would not
trip over. For example, if BIOS described a device in ACPI but didn't
mention it in E820, Windows would work fine but Linux would fail.
Reference: https://bugzilla.kernel.org/show_bug.cgi?id=16228
Acked-by: H. Peter Anvin <hpa@zytor.com>
Signed-off-by: Bjorn Helgaas <bjorn.helgaas@hp.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
2010-12-17 00:38:56 +07:00
|
|
|
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;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void remove_e820_regions(struct resource *avail)
|
|
|
|
{
|
|
|
|
int i;
|
|
|
|
struct e820entry *entry;
|
|
|
|
|
2016-09-18 04:39:26 +07:00
|
|
|
for (i = 0; i < e820->nr_map; i++) {
|
|
|
|
entry = &e820->map[i];
|
x86: avoid E820 regions when allocating address space
When we allocate address space, e.g., to assign it to a PCI device, don't
allocate anything mentioned in the BIOS E820 memory map.
On recent machines (2008 and newer), we assign PCI resources from the
windows described by the ACPI PCI host bridge _CRS. On many Dell
machines, these windows overlap some E820 reserved areas, e.g.,
BIOS-e820: 00000000bfe4dc00 - 00000000c0000000 (reserved)
pci_root PNP0A03:00: host bridge window [mem 0xbff00000-0xdfffffff]
If we put devices at 0xbff00000, they don't work, probably because
that's really RAM, not I/O memory. This patch prevents that by removing
the 0xbfe4dc00-0xbfffffff area from the "available" resource.
I'm not very happy with this solution because Windows solves the problem
differently (it seems to ignore E820 reserved areas and it allocates
top-down instead of bottom-up; details at comment 45 of the bugzilla
below). That means we're vulnerable to BIOS defects that Windows would not
trip over. For example, if BIOS described a device in ACPI but didn't
mention it in E820, Windows would work fine but Linux would fail.
Reference: https://bugzilla.kernel.org/show_bug.cgi?id=16228
Acked-by: H. Peter Anvin <hpa@zytor.com>
Signed-off-by: Bjorn Helgaas <bjorn.helgaas@hp.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
2010-12-17 00:38:56 +07:00
|
|
|
|
|
|
|
resource_clip(avail, entry->addr,
|
|
|
|
entry->addr + entry->size - 1);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2010-12-17 00:38:51 +07:00
|
|
|
void arch_remove_reservations(struct resource *avail)
|
|
|
|
{
|
2014-07-16 15:00:57 +07:00
|
|
|
/*
|
|
|
|
* 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.
|
|
|
|
*/
|
2010-12-17 00:38:51 +07:00
|
|
|
if (avail->flags & IORESOURCE_MEM) {
|
2010-12-17 00:39:02 +07:00
|
|
|
resource_clip(avail, BIOS_ROM_BASE, BIOS_ROM_END);
|
x86: avoid E820 regions when allocating address space
When we allocate address space, e.g., to assign it to a PCI device, don't
allocate anything mentioned in the BIOS E820 memory map.
On recent machines (2008 and newer), we assign PCI resources from the
windows described by the ACPI PCI host bridge _CRS. On many Dell
machines, these windows overlap some E820 reserved areas, e.g.,
BIOS-e820: 00000000bfe4dc00 - 00000000c0000000 (reserved)
pci_root PNP0A03:00: host bridge window [mem 0xbff00000-0xdfffffff]
If we put devices at 0xbff00000, they don't work, probably because
that's really RAM, not I/O memory. This patch prevents that by removing
the 0xbfe4dc00-0xbfffffff area from the "available" resource.
I'm not very happy with this solution because Windows solves the problem
differently (it seems to ignore E820 reserved areas and it allocates
top-down instead of bottom-up; details at comment 45 of the bugzilla
below). That means we're vulnerable to BIOS defects that Windows would not
trip over. For example, if BIOS described a device in ACPI but didn't
mention it in E820, Windows would work fine but Linux would fail.
Reference: https://bugzilla.kernel.org/show_bug.cgi?id=16228
Acked-by: H. Peter Anvin <hpa@zytor.com>
Signed-off-by: Bjorn Helgaas <bjorn.helgaas@hp.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
2010-12-17 00:38:56 +07:00
|
|
|
|
|
|
|
remove_e820_regions(avail);
|
2010-12-17 00:38:51 +07:00
|
|
|
}
|
|
|
|
}
|