Re: Why such a big difference in init-time PCI resource call-paths (x86 vs x86_64) ?

[Jesse Barnes]

On Thursday, May 01, 2008 1:11 pm H. Peter Anvin wrote:
> Andi Kleen wrote:
> > On Thu, May 01, 2008 at 11:16:31AM -0700, Jesse Barnes wrote:
> >> On Wednesday, April 30, 2008 9:07 am TJ wrote:
> >>> In preparation for writing a Windows-style PCI resource allocation
> >>> strategy
> >>>
> >>>  - use all e820 gaps for IOMEM resources; top-down allocation -
> >>>
> >>> and thus giving devices with large IOMEM requirements more chance of
> >>> allocation in the 32-bit address space below 4GB (see bugzilla #10461),
> >
> > I tried that some time ago and it turned out that some systems have
> > mappings in holes and don't boot anymore when you fill the holes too
> > much. But that was only considering e820. if you do this it might work if
> > you do it really like windows and consider all resources, including ACPI.
>
> Yes, considering all possible reservation schemes is really critical
> here (including the magic knowledge of the legacy region).

Yeah, good point.  There's code to check for ACPI reserved regions when 
verifying MCFG space, so at least we're starting to do this...

Thanks,
Jesse

--
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/