> > On x86 platforms, there are two sources through which kernel learns > > about physical memory in the system namely E820 table and EFI Memory > > Map. Each table describes which regions of system memory is usable by > > kernel and which regions should be preserved (i.e. reserved regions > > that typically have BIOS code/data) so that no other component in the > > system could read/write to these regions. I think they are duplicating > > the information and hence I have couple of questions regarding these > > > > 1. I see that only E820 table is being consumed by kernel [1] (i.e. > > memblock subsystem in kernel) to distinguish between "usable" vs "reserved" > regions. > > Assume someone has called memblock_alloc(), the memblock subsystem > > would service the caller by allocating memory from "usable" regions > > and it knows this *only* from E820 table [2] (it does not check if EFI > > Memory Map also says that this region is usable as well). So, why > > isn't the kernel taking EFI Memory Map into consideration? (I see that > > it does happen only when "add_efi_memmap" kernel command line arg is > > passed i.e. passing this argument updates E820 table based on EFI > > Memory Map) [3]. The problem I see with memblock not taking EFI Memory > > Map into consideration is that, we are ignoring the main purpose for which EFI > Memory Map exists. > > https://blog.fpmurphy.com/2012/08/uefi-memory-v-e820-memory.html > Probably above blog can explain some background. Thanks a lot! Dave. The link was helpful, it did explain that Linus and HPA were not very happy with EFI and things were going good with E820 and hence it was given more preference compared to EFI. But sadly, I am not 100% convinced yet :( (just my thoughts) This decision was made a decade ago when EFI wasn't stable. Now that UEFI is the defacto on most of the x86 platforms (and since I believe UEFI is getting better) I am still unable to digest that kernel throws away EFI Memory Map (unless explicitly asked by "add_efi_memap") Regards, Sai
