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

Vivek Goyal vgoyal at redhat.com
Thu Oct 24 15:27:52 EDT 2013


On Thu, Oct 24, 2013 at 12:24:57PM -0700, Yinghai Lu wrote:
> On Thu, Oct 24, 2013 at 12:18 PM, Vivek Goyal <vgoyal at redhat.com> wrote:
> > On Thu, Oct 24, 2013 at 12:15:25PM -0700, Yinghai Lu wrote:
> >
> > Also keeping things simple by not trying to *impose* a new crashkernel=
> > syntax on existing crashkernel=xM users.
> 
> Existing user that have crashkernel=xM working with their old kernel
> and old kexec-tools, they still could keep their old command line and
> old kexec-tools
> with new updated kernel.
> We should not change semantics to surprise them.

Old users will get reservation still below 896MB.

It will go above 896MB only if memory could not be allocated below 896MB.

In the past reservation will fail and kexec-tools will fail.
Now reservation will succeed but kexec-tools will fail.

So end result a user sees is that kexec-tools fails. So I don't see how
we are breaking existing installations or user setups.

Thanks
Vivek



More information about the kexec mailing list