Re: [PATCH] x86, kdump: crashkernel=X try to reserve below 896Mfirst, then try below 4G, then MAXMEM

[Vivek Goyal]

On Thu, Oct 24, 2013 at 12:13:41PM -0700, Yinghai Lu wrote:

[..]
> old kexec-tools could work cross 892M in some case.
> That will confuse the user,

If it could work beyong 892MB, then why are you limiting user to 896MB
only. That sounds wrong.

> as it works some time on some setup, but does
> not work on other setup.

If it can work above 896MB, then those other setup should be fixed.

All the existing users of crashkernel=xM *will not* be affected by this
change. Memory reservation will still be below 892MB.

Memory reservation will gove above 896MB, only if user chooses to reserve
more memory. If kexec works in that case, its a win-win situation. If it
does not and fails, then it is status quo is maintained.

Thanks
Vivek
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/