On Mon, Mar 11, 2013 at 12:44:15PM -0700, Yinghai Lu wrote: > On Mon, Mar 11, 2013 at 12:39 PM, Yinghai Lu <ying...@kernel.org> wrote: > > On Mon, Mar 11, 2013 at 12:38 PM, Vivek Goyal <vgo...@redhat.com> wrote: > >>> No need to use crashkernel_high, we can just cashkernel=X@Y instead. > >> > >> crashkernel=X@Y is little different. It assumes user knows the memory > >> map and location "Y" is fixed. There might not be any memory at "Y". > > > > then use crashkernel=4G? > > I re attached -v2 and -v3. > > I'm ok that any one is applied or two get applied all together. > > only affect 64bit > -v2: try under under 896M, then 4G, then MAXMEM > -v3: auto set crashkernel_low with swiotlb size.
So, what's the resolution on this issue. Is the verdict that we always reserve high. Update your kexec-tools to cope with that. For swiotlb issue, modify kexec-tools to copy low memory in backup region and give low memory to second kernel for software iotlb? I am assuming that updating tools will not help with loading and using of 32bit bzImage. So user needs to use crashkernel=X@Y syntax to cope with that? (Given the fact that copying code around after crash carries the greater risk of ongoing DMA on destination location). 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/
