Looking a little more closely at the users there
is a clear demand in the kernel for some kind of forced
reboot. Coming from software watchdog timers and the like,
and it makes sense for sysrq-b to call the same thing.
However I'm not at all certain that we want the software is
hosed reboot dammit, to be the same as the graceful reboot
path.
There are a lot of things we can do on the graceful reboot
path like switch to the bootstrap cpu, attempt to make BIOS
calls to perform the reboot etc, that I'm not at all certain
we want to perform on the under more dire circumstances.
If it weren't simply overkill I'd say in the freaked out kernel
reboot case we want to kexec to a sane kernel and then reboot from
there.
Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
