Given that the kexec code is tied intimately to the kernel
Given that there is no real advantage in an incremental write
model for kexec users (except not needing to allocate a syscall
Do you see a better way to structure the kexec interface?
Another file in proc, not carefully placed is just a hair better than
an ioctl. Using /proc is not desirable because there are uses of
kexec that need a very small kernel, and /proc is a pig, is otherwise
useless size bloat.
For some uses including the one that drove me to write it CONFIG_KEXEC
and CONFIG_TINY will both be defined.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/