Re: [PATCH v2] Do not reserve crashkernel high memory if crashkernel low memory reserving failed

From: Joerg Roedel
Date: Mon Jul 27 2015 - 10:46:04 EST


On Tue, Jul 21, 2015 at 09:38:14AM +0200, Ingo Molnar wrote:
> Also, why was this syntax introduced in the first place? Why should the user
> care??
>
> We should only have a single crashkernel option, to enable it - and everything
> else should be figured out by the kernel, automatically.
>
> Any other sub-options just paper over some fragility elsewhere and make the
> feature harder to use, hence more fragile.

Hmm, maybe the reason is that old userspace (kdump/kexec tools) can't
deal with crashkernel loaded high, so that the default for
crashkernel=size allocations was kept to be under 896MB.

If that's not an issue we can change the default and get rid of the
,high and ,low syntax.


Joerg

--
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/