On Tue, Apr 2, 2013 at 12:11 PM, Vivek Goyal <vgo...@redhat.com> wrote: > On Tue, Apr 02, 2013 at 11:49:13AM -0700, Yinghai Lu wrote: >> On Tue, Apr 2, 2013 at 11:42 AM, Yinghai Lu <ying...@kernel.org> wrote: >> > aka: >> > old kexec-tools stay with "crashkernel=X" >> > new kexec-tools stay with >> > 1. like old kexec tools >> > 2. or "crashkernel=X,high" or "crashkernel=X,high crashkernel=Y,low", >> > Y could be 100M or 0 etc. >> >> I keep the old logic like: >> if there are several "crashkernel=X,high", only last one is honored. >> if there are several "crashkernel=Y,low", only last one is honored. > > Yes but if different types of crashkernel= options are mixes then > behavior is not defined.
dmesg or /proc/iomem will show them what is finally reserved. > > crashkernel=X,high crashkernel=X ==> crashkernel=X is tossed away. > crashkernel=X,high crashkernel=Y;low normal case. if user want more or disable low range. > crashkernel=Y;low crashkernel=X crashkernel=X will be used. > > And possibilities go on. So I think it makes life simpler if we always > parse last crashkernel= option and act upon that. And use > crashkernel_no_auto_low to opt out of auto reserved low memory area. No, that is not just disable. User could want more like 128M instead of 72M. Thanks Yinghai -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/