Messages in this thread | | | Date | Tue, 15 Mar 2011 15:52:38 +0800 | Subject | Re: [PATCH 1/2] kdump: Allow shrinking of kdump region to be overridden | From | Américo Wang <> |
| |
On Tue, Mar 15, 2011 at 2:13 AM, Mahesh J Salgaonkar <mahesh@linux.vnet.ibm.com> wrote: > > During free we do free all of them including RMO region. But since the rtas > region is always on top of RMO, crashkernel memory overlaps rtas region and > we endup freeing that even, which is causing the crash. >
Okay, but with this patch applied, we will just ignore rtas region, right? Thus, when I echo 0 to free all the 128M crashkernel memory, the final result will be 32M left, which means crash_size will still show 32M. This looks odd.
How about skipping the 32M as a whole? I mean once the region being freed has overlap with this rtas region, skip the whole rtas region, and let crash_size show 0?
Thanks.
| |