On Mar 27, 2008, at 7:45 PM, Michael Ellerman wrote:
On Fri, 2008-03-28 at 10:14 +1100, Paul Mackerras wrote:
Kumar Gala writes:
@@ -1124,7 +1124,7 @@ void __init early_init_devtree(void *params)
parse_early_param();
/* Reserve LMB regions used by kernel, initrd, dt, etc... */
- lmb_reserve(PHYSICAL_START, __pa(klimit) - PHYSICAL_START);
+ lmb_reserve(__pa(_stext), _end - _stext);
In the kdump case where the kernel starts at the 32MB point
(physical), wouldn't we want to reserve the first 32MB of RAM so that
it can't get allocated and used for random things? Doesn't that
first
32MB contain the old kernel that we want to write out?
For kdump there is nMB of memory reserved at 32MB for the 2nd kernel,
and that's all it gets, all of the other memory is the old kernel text
or the old kernel's data.
My understanding is those reservations are handled by the device tree
that is passed to the 2nd kernel.
- k
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
