Re: PCI memory allocation bug with CONFIG_HIGHMEM

[Russell King]

On Wed, Jan 07, 2004 at 08:06:04AM -0700, Eric W. Biederman wrote:
> 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);

I was hoping someone was going to take my comments as a suggestion for
a possible solution to the problem.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 PCMCIA      - http://pcmcia.arm.linux.org.uk/
                 2.6 Serial core
-
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/