> > So I'm not still sure about what are advantages of a property under /chosen > > over "memmap=" kernel parameter. > > Both are simple and can have the same effect with minimizing changes to dtb. > > (But if, in the latter case, we have to provide *all* the memory-related information > > through "memmap=" parameters, it would be much complicated.) > > Maybe I did not say it clearly, I prefer kexec syscall/tool to modifiy dtb > or uefi-memmap so that we do not need any extra kernel cmdline. > > For x86 we would like to drop the memmap= usage in kexec-tools but we can not > do that for a compatibility problem about calgary iommu. So that currently > kexec-tools supports both recreating E820 maps and passing memmap=. > > We should think it carefully because it will be hard to remove once we support it. > IMO handling it in code is better than using an external interface. > Also seems semantic of memmap=exactmap is different than current use in the implementation exactmap means we need pass each range seperately including reserved, acpi and other types We can not reuse ranges in uefi memmap for other than usable memory. It will also have the cmdline array size issue. Thanks Dave
