Messages in this thread |  | | | Date | Fri, 4 May 2012 12:22:58 -0700 | | Subject | Re: [RFC PATCH] Expand memblock=debug to provide a bit more details (v1). | | From | Yinghai Lu <> |
| |
On Fri, May 4, 2012 at 11:49 AM, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote: > While trying to track down some memory allocation issues, I realized that > memblock=debug was giving some information, but for guests with 256GB or > so the majority of it was just: > > memblock_reserve: [0x00003efeeea000-0x00003efeeeb000] __alloc_memory_core_early+0x5c/0x64 > > which really didn't tell me that much. With these patches I know it is: > > memblock_reserve: [0x00003ffe724000-0x00003ffe725000] (4kB) vmemmap_pmd_populate+0x4b/0xa2 > > .. which isn't really that useful for the problem I was tracking down, but > it does help in figuring out which routines are using memblock. >
that RET_IP is not very helpful for debugging.
Actually I have local debug patch for memblock. please check if that is going to help debugging.
Thanks
Yinghai [unhandled content-type:application/octet-stream][unhandled content-type:application/octet-stream] |  |