[PATCH 5/5] kexec: X86: Pass memory ranges via e820 table instead of memmap= boot parameter

H. Peter Anvin hpa at zytor.com
Tue Apr 16 07:59:35 EDT 2013

It is not. Read the boot spec.

Thomas Renninger <trenn at suse.de> wrote:

>On Monday, April 15, 2013 12:54:47 PM H. Peter Anvin wrote:
>> 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
>> >> they just have to be passed via a different mechanism.
>But you do not name/describe it.
>Is it the "efi map mechanism" you are talking about or is there
>something else?
>      Thomas
>> > 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
>> > 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
>> of pain.
>> 	-hpa

Sent from my mobile phone. Please excuse brevity and lack of formatting.

More information about the kexec mailing list