[PATCH 5/5] kexec: X86: Pass memory ranges via e820 table instead of memmap= boot parameter
H. Peter Anvin
hpa at zytor.com
Mon Apr 15 15:54:47 EDT 2013
On 04/15/2013 12:48 PM, Thomas Renninger wrote:
> On Monday, April 15, 2013 05:20:24 AM H. Peter Anvin wrote:
>> Except that is wrong. The kernel can receive more than 128 e820 entries,
>> they just have to be passed via a different mechanism.
> Would it make sense to pass the tables via efi_map by moving up
> efi_map parsing to the beginning of efi init in arch/x86/platform/efi/efi.c?
> And in kexec pass the efi signature, efi map pointers, add add_efi_memmap
> param (and possibly some more?)?
> Then there would be no limit at all anymore.
There is no limit... that's what I'm telling you.
kexec should certainly pass the EFI information, otherwise the second
kernel can't invoke EFI runtime calls at all. Therein lies a whole bit
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
More information about the kexec