> The good news is that it worked for me. Not only that, I have just
> managed to get lkcd to save a dump in memory and then write it out
> to disk after a kexec soft boot ! I haven't tried real panic cases yet
> (which probably won't work rightaway :) ) and have testing and
> tuning to do. But kexec seems to be looking good.
Nice. Any pointers besides lkcd.sourceforge.net
For the kexec on panic case there is a little code motion yet to be
done so that no memory allocations need to happen. The big one is
setting up a page table with the reboot code buffer identity mapped.
I am tempted to do the identity mapping of the reboot code buffer in
init_mm, but for starters I will look at how complex it will be to
have a spare mm just sitting around for that purpose. When I get
to dealing with the architectures like the hammer, and the alpha where
you always need page tables I will need to develop an architecture
specific hook for building the page tables needed by the
code residing in the reboot code buffer, (because virtual memory
cannot be disabled), but that should be straight forward.
My goal is to have no locks on the kexec part of the panic path. And
the current memory allocations are the only really bad part of that.
A dump question. Why doesn't the lkcd stuff use the normal ELF core
dump format? allowing ``gdb vmlinux core'' to work?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/