Re: kexec on ppc64

[Dave Hansen]

taking silly IBM list off the cc...

On Wed, 2004-07-14 at 07:45, R Sharada 
>         - also identify relevant data (that might be required for the
> kexec kernel) that could be pushed into the device_tree so that it can
> be passed to the new kexec kernel

We actually had a similar problem on x86.  The e820 table is presented
by the BIOS, and must be saved or reconstructed when you boot into the
new kernel.  

It would be really cool to have a way of passing the memory layout
information to the new kernel that is relatively cross-platform.  That
way, we don't get stuck rewriting it for each new arch.  

For instance, instead of passing the BIOS/firmware structures like LMBs 
in the device tree or e820 tables to the kexec kernel, you'd pass the
Linux concepts like zone_start_pfn and so forth.

> I would like to solicit inputs, feedback, opinions, changes on this
> preliminary idea and planned list of 'things to do'. I would also like
> to know the interest to participate in this effort or anything else
> related to 'kexec on ppc64'.

While you're ripping apart prom.c, have you thought about getting rid of
all of the RELOC() stuff?  I think Ben H. had an evil plan for that,
too.

BTW, have you seen any opportunities to replace the arch-specific things
like lmb_alloc() with normal bootmem calls?

-- Dave

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/