![]() | |||||||||||
Messages in this thread |
Vivek Goyal wrote: > On Thu, Aug 10, 2006 at 02:09:58PM -0600, Eric W. Biederman wrote: >>> I just reserved memory at non 2MB aligned location 65MB@15MB so that >>> kernel is loaded at 16MB and other smaller segments below the compressed >>> image, then I can successfully booted into the kdump kernel. >> :) >> >>> So basically kexec on panic path seems to be clean except stomping issue. >>> May be bzImage program header should reflect right "MemSize" which >>> takes into account extra memory space calculations. >> Yes. That sounds like the right thing to do. >> >> I remember trying to compute a good memsize when I created the bzImage >> header but it is completely possible I missed some part of the >> calculation or assumed that the kernels .bss section would always be >> larger than what I needed for decompression. >> Could someone please describe the intended semantics of this MemSize header, *and* its intended usage? -hpa - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||
| Last update: 2006-08-14 19:09 [from the cache] ©2003-2008 | |||||||||||