Re: PCI memory allocation bug with CONFIG_HIGHMEM

[Eric W. Biederman]

Russell King <rmk+lkml@xxxxxxxxxxxxxxxx> writes:

> On Tue, Jan 06, 2004 at 09:58:23PM -0700, Eric W. Biederman wrote:
> > ffff0000-ffffffff : reserved
> > 
> > That last reserved region is 64K.  Which looking at the pci registers
> > is technically correct at the moment.  Only 64K happen to be decoded.
> 
> We already have this distinction between in use (or busy) resources and
> allocated resources.  Surely the BIOS ROM region should be an allocation
> resource not a busy resource, so that the MTD driver can obtain a busy
> resource against it?

Nope the BIOS region is allocated as BUSY, at least as it comes
out of the E820 map.

>From arch/i386/kernel/setup.c:legacy_init_iomem_resources
....
		res -> start = e820.map[i].addr;
		res -> end = res->start + e820.map[i].size - 1;
		res -> flags = IORESOURCE_MEM | IORESOURCE_BUSY;
		request_resource(&iomem_resource, res);

Eric



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/