On Fri, Mar 22, 2013 at 2:21 PM, Vivek Goyal <vgoyal at redhat.com> wrote: >> > In case of kexec_on_panic, we seem to have all the memory ranges in >> > info->memory_ranges[]. I guess we don't need that. We just need ranges >> > which are reserved for crash kernel and marked by "Crash Kernel". In >> > that case we will be able to handle multiple "Crash Kernel" ranges. >> >> but we still like to put kernel and initrd high, and leave low range >> for swiotlb. >> could just find mem_min and mem_max for largest and last one. > > Yes, but I guess that should not be hard coded here. It is during load > phase we should enforce where we want to load all the segments. > > It will work though for our current usage. May be later we can improve > it further. Where loader sees all the memory ranges (low and high) and > we choose appropriate segment. ok.
