> Presumably your user-mode kernel would want to run binaries
> for the same arch it was built for, and have a way to reroute
> syscalls to the pseudo-kernel rather than the real kernel.
PTRACE_SYSCALL. annul the syscall. do what you want to the target
process.
> Worse yet, I see no obvious way for this 'user-mode' kernel to do
> the necessary memory remapping it would need for its processes.
> Being run inside of the same real process, they would have the
> same view on memory.
In my view of the world, every process would be a direct child of
the user-mode kernel (UMK). The UMK would handle the pseudo-parent-
and-child relationships by proxy'ing syscalls such as wait and
ptrace.
I have no clue how to handle things like device drivers, but I have
some of the puzzle pieces for the syscall filtering layer for a UMK.
Michael Elizabeth Chastain
<mailto:mec@shout.net>
"love without fear"
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/