Re: [PATCH 0/3] Cleanup kdump memmap= passing and e820 usage

Yinghai Lu
2013-01-30T17:41:22Z

On Wed, Jan 30, 2013 at 8:52 AM, H. Peter Anvin <hpa@zytor.com> wrote:
> The e820 map is fundamentally what you care about, and it has to be passed
> correctly anyway -- or your changes are utterly broken. The modifications
> that have to be performed (from RAM to KDUMP) is trivial.
>
> I have to admit to being rather confused as to the separation of various
> bits of kdump between the host kernel and various user-space components, but
> the whole use of the command line to pass the memory map seems just broken
> in light of everything that can go wrong.

Thomas,

Can you try to work out patch for kexec-tools that kdump change all
ram to KDUMP_RESERVED,
and only make crask_kernel in /proc/iomem to be RAM type?

then we only kernel patch for kdump will check KDUMP_REDREVED and RAM
type to get saved_max_pfn.

Thanks

Yinghai