On Tue, Apr 02, 2013 at 08:46:16AM -0700, Yinghai Lu wrote: > On Tue, Apr 2, 2013 at 8:39 AM, Vivek Goyal <vgo...@redhat.com> wrote: > > On Tue, Apr 02, 2013 at 07:45:36AM -0700, Yinghai Lu wrote: > > > > [..] > >> 2. keep thing unified when new kexec-tools is used: always high. > > > > I think this is wrong. What if system does not have more than 4G of > > memory. crashkernel=x,high will fail. So just because we have new version > > of kexec-tools, it does not mean that one can always use crashkernel=x,high. > > no, it will not fail. > > If the system have less 4G, and memblock will still find the ram for us.
Ok, then description in kernel-parameters.txt is wrong. + crashkernel_high=size[KMG] + [KNL, x86_64] range above 4G. kernel allocate physical + memory region above 4G. Can you please inline your patches. Otherwise how one is supposed to give review comments? Thanks Vivek -- 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/
