On Wed, 26 Mar, at 01:22:49PM, Jan Beulich wrote: > >>> On 26.03.14 at 14:00, <matt@xxxxxxxxxxxxxxxxx> wrote: > > > > This could do with a little bit more explanation. Why is it not > > necessary to mark the EFI memory map that was passed to the kernel as > > reserved in memblock? > > Because that's in memory Dom0 doesn't even see: The EFI memory > map is visible to the hypervisor only. So where does boot_params.efi_info.efi_memmap point? If nowhere (i.e. it's NULL) that's no problem because memblock_reserve() handles zero size regions just fine. -- Matt Fleming, Intel Open Source Technology Center -- To unsubscribe from this list: send the line "unsubscribe linux-efi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
