Matt, The kernel I referring is the boot kernel aka the 1st kernel, the boot loader is grub2 from Fedora 19. [sorry for top reply because of using webmail] ----- Original Message ----- From: "Matt Fleming" <matt@xxxxxxxxxxxxxxxxx> To: "Dave Young" <dyoung@xxxxxxxxxx> Cc: "Borislav Petkov" <bp@xxxxxxxxx>, "X86 ML" <x86@xxxxxxxxxx>, "LKML" <linux-kernel@xxxxxxxxxxxxxxx>, "Borislav Petkov" <bp@xxxxxxx>, "Matthew Garrett" <mjg59@xxxxxxxxxxxxx>, "H. Peter Anvin" <hpa@xxxxxxxxx>, "James Bottomley" <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>, "Vivek Goyal" <vgoyal@xxxxxxxxxx>, linux-efi@xxxxxxxxxxxxxxx, fwts-devel@xxxxxxxxxxxxxxxx Sent: Friday, October 11, 2013 6:27:06 PM Subject: Re: [PATCH 12/12] EFI: Runtime services virtual mapping On Fri, 11 Oct, at 02:24:37PM, Dave Young wrote: > For the boot efi_reserve_boot_services code, it's mainly for the > SetVirtualAddressMap callback use, so boot regions should not be reused > before SetVirtualAddressMap, but the overlapping happens before the > efi_reserve_boot_services, isn't it a problem? Hang on, which kernel are you referring to here? The boot kernel or the kexec'd kernel? I thought you were saying you noticed the overlap when running in the second (kexec'd) kernel? The only reason that you would see this overlap in the first (boot) kernel is if the bootloader messed up and allocated the kernel text as EfiBootServicesCode/Data. I'd like to believe no bootloaders are still doing that. -- Matt Fleming, Intel Open Source Technology Center -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ -- 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
