On Wed, Mar 10, 2010 at 04:02:07PM -0800, Yinghai Lu wrote: > On 03/10/2010 03:47 PM, Benjamin Herrenschmidt wrote: > > On Wed, 2010-03-10 at 14:36 -0800, David Miller wrote: > >> LMB could do this too with minor modifications. > >> > >> Simply make the lmb.memory and lmb.reserved be pointers, and initially > >> they point into the static array(s). > >> > >> Later the pointers can be repositioned to point to dynamically > >> allocated memory. > >> > >> So please, for the third time, please show me how LMB with some minor > >> modifications is not able to satisfy your needs. > > > > So I was about to say the exact same stuff here... > > > let see: > 1. if early_res + fw_memmap could be simplified... > 2. or let x86 to use lmb instead of early_res,then add more to lmb. > I vote for LMB too, it's already used across multiple architectures and has proven to be quite versatile. If x86 is concerned about consolidation, then it's a good a place to start as any, particularly since it's not even that conceptually different from how the e820 maps are used. This may come as a surprise, but if this had actually been brought up on linux-arch instead of buried in -tip and magically showing up in -next everyone involved could have saved a lot of time. -- To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html