Feng Tang wrote: > > Hi hpa, > > I understand your concern, and I've added that code into our boot loader > for Moosrestown which sets up a e820 memory table in boot parameters by > parsing SFI table. > > The reason we still keep this piece of code is to be compatible with old > version boot loaders which may not know SFI info yet. And > sfi_init_memory_map() only get called when kernel can't find an e820 table > in boot parameters. > > Anyway, I think we can remove the code if it really breaks the rule. > > Thanks, > Feng > What I'm concerned about is that we will want to be able to use the range allocator, which relies on the e820 memory map, extremely early during boot. In the EFI case, we allow (*optionally*) to fill in additional information from the EFI map after initial boot, but we still require memory ranges in the initial map (they can, however, be a subset of the available memory.) I'm really concerned about saying "well, it works now" and tying ourselves into an interface that we cannot support in the long term (read: we'll be stuck with it.) -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf. -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
