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. I think we should do two things. - Extend crashkernel=X to search for memory below 896M, 4G, MAXMEM in that order. To me, this will work best for most of the users. - For users who really care to not allocate memory in low memory ranges, they can use crashkernel=X,high. But even there syntax should be that look for memory in higher ranges first otherwise allocate from low regions. Otherwise it makes life very difficult for a user when there is no memory available in higher addresses but it is available in low addresses. How does one automate that. In current form, I double crashkernel=X,high is going to be very useful. 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/
