On Wed, Oct 23, 2013 at 10:17:31AM +0800, Dave Young wrote: > The reason is that I only pass runtime regions from 1st kernel to > kexec kernel, your efi mapping function uses the region size to > determin the virtual address from top to down. Because the passed-in > md ranges in kexec kernel are different from ranges booting from > firmware so the virtual address will be different. Well, this shouldn't be because SetVirtualAddressMap has already fixed the virtual addresses for us. And if they're different, then runtime services won't work anyway. Or am I missing something...? > Even I pass the whole untouched ranges including BOOT_SERVICE there's > still chance the function for reserving boot regions overwrite the > boot region size to 0, and 1st kernel will leave it to be used as > normal memory after efi init. I think we have talked about this issue > previously. Matt, didn't you question the need to keep boot services regions mapped indefinitely? What was the story there? Thanks. -- 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
