On Fri, 14 May 2010 16:40:55 -0700 "H. Peter Anvin" <hpa@xxxxxxxxx> wrote: > On 05/14/2010 04:33 PM, Jesse Barnes wrote: > > > > As for BIOS coordination for dynamic reallocation, yeah there'd be some > > of that. I think the basic principles would be: > > 1) use BIOS allocations wherever possible > > 2) get an accurate list of available resources from the BIOS for > > potential remapping later > > 3) allocate resources for BARs and devices as late as possible (e.g. > > at driver bind time) to avoid allocating more than we need > > > > But that's a good chunk of work, and as we've seen, PCs in particular > > are really sensitive to having resources moved around too much, so step > > (2) is probably the hardest part. > > > > The real problem that I see, as outlined before, has nothing to do with > the BIOS, but rather the interdependencies between resources. I was using the term "BIOS" loosely to refer to safe ranges to allocate resources. Your topology example is a good one, there are definite dependencies between devices, especially on large systems. But in both simple and complex cases, we still need to have resource ranges available, or we'll have no where to put things at all. -- Jesse Barnes, Intel Open Source Technology Center -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
