On 12/21/2011 10:28 PM, Dave Anderson wrote: > > And complicating matters even further, your patch presumes that the > kernel has configured CONFIG_SPARSEMEM_EXTREME in conjunction with > CONFIG_SPARSEMEM. Would it be possible for an s390x to be configured > with just CONFIG_SPARSEMEM alone? Not sure. I have never tried building s390x kernel configured with just CONFIG_SPARSEMEM alone. > If so, your patch breaks down. > > Or is there another way you can determine which MAX_PHYSMEM_BITS value > is in use? This value is a #define constant and I dont see any kernel symbol holding this value which could have been easy way to determine this value. Thanks, -Mahesh. -- Crash-utility mailing list Crash-utility@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/crash-utility
