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

Thomas Renninger trenn at suse.de
Tue Apr 16 03:52:36 EDT 2013

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 entries,
> >> 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?


> > 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
> of pain.
> 	-hpa

More information about the kexec mailing list