On Tue, 2002-11-05 at 19:19, Werner Almesberger wrote:
> kexec needs:
> - a system call to set it up
Device, file, insmod...
> - a way to silence devices (difference to dumper: kexec normally
> operates under an intact system, so it's more similar to, say,
> swsusp. But I expect that cleaning up device power management
> would also clear the path for more reliable dumpers.)
So you need to register with the power management as the last thing to
be suspended and do a suspend before kexec.
> So not merging it is mainly inconvenient to use, adds the system
> call allocation as a continuous annoyance, and makes it a little
> harder to work on the related infrastructure. But then, despite
> being somewhat obscure, bootimg and kexec have been in use for
> years, the design is about as lean as it can get, and it's cool.
> What more could you ask for ? :-)
I'm mostly worried about how to make these things fit the least
intrusively into the kernel.
-
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/
This archive was generated by hypermail 2b29 : Thu Nov 07 2002 - 22:00:39 EST