> > > Let me ask the same dumb question - what does kexec need that a dumper
> > > doesn't.
> >
> > kexec needs:
> > - a system call to set it up
> > - a way to silence devices <snip>
> <snip>
> > - a bit of glue <snip>
> > - device drivers that can bring silent devices back to life
> <snip>
>
> > > In other words given reboot/trap hooks can kexec happily live
> > > as a standalone module ?
>
> You could probably skip the system call to set it up. Example: I could
> imagine a bizarre set of pseudo-devices:
>
> # insmod kexec
> # cat bzImage > /proc/kexec/next-image
> # echo "root=805" > /proc/kexec/next-cmndline
> # echo 1 > /proc/kexec/reboot
>
> and hide away that dirty little sequence with a nice kexec(3) library
> routine.
Actually, sys_reboot has void * parameter. Reusing it as "next-image"
char * seems okay to me.
Pavel
-- Worst form of spam? Adding advertisment signatures ala sourceforge.net. What goes next? Inserting advertisment *into* email? - 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/