Re: [PATCH 0/3] Make use of new memmap= kernel parameter syntax

H. Peter Anvin
2013-01-30T05:41:48Z

The right thing to do as I have discussed with the people involved is to modify the memory map data structure to have a new memory type ID for memory which is to be dumped. That eliminates the need to put all this info into the command line.

Simon Horman <horms@verge.net.au> wrote:

>On Tue, Jan 22, 2013 at 04:02:12PM +0100, Thomas Renninger wrote:
>> Details were discussed on quite some lists (kexec, lkml, x86, etc)
>> in a kernel thread with subject:
>> [PATCH] x86 e820: only void usable memory areas in memmap=exactmap
>case
>>
>> The patch that memmap= can take several arguments is already queued
>> in linux-x86-tip in the mm2 branch.
>>
>> There have been no objections on the introduction to
>memmap=resetusablemap
>> for several days after discussing things in detail. The repost
>patches
>> (will do that now) propably will show up in x86-tip mainline kernel
>> tree pretty soon as well.
>> Target for this feature to show up in Linus' tree is 3.9-rc1.
>> Therefore these patches check for 3.9.0 and newer kernels. If such a
>> kernel is tried to get loaded via kexec -p, the new memmap= syntax is
>used.
>>
>> Please consider to apply these to the kexec-tools repository.
>
>Hi Thomas,
>
>could I check that the status of these patches is still as you describe
>above?

--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.