>>> On 26.03.14 at 14:00, <matt@xxxxxxxxxxxxxxxxx> wrote: > On Tue, 25 Mar, at 09:57:54PM, Daniel Kiper wrote: >> Call efi_memblock_x86_reserve_range() on native EFI platform only. >> This is not needed and even it should not be called on platforms >> which wraps EFI infrastructure like Xen. >> >> Signed-off-by: Daniel Kiper <daniel.kiper@xxxxxxxxxx> >> --- >> arch/x86/kernel/setup.c | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >> >> diff --git a/arch/x86/kernel/setup.c b/arch/x86/kernel/setup.c >> index ce72964..992b67a 100644 >> --- a/arch/x86/kernel/setup.c >> +++ b/arch/x86/kernel/setup.c >> @@ -933,7 +933,7 @@ void __init setup_arch(char **cmdline_p) >> set_bit(EFI_64BIT, &x86_efi_facility); >> } >> >> - if (efi_enabled(EFI_BOOT)) >> + if (!strncmp((char *)&boot_params.efi_info.efi_loader_signature, "EL", 2)) >> efi_memblock_x86_reserve_range(); >> #endif > > 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. Jan -- 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
