The signal return code was trying to access user mode addresses
authorMatthew Dillon <dillon@dragonflybsd.org>
Mon, 8 Jan 2007 08:17:17 +0000 (08:17 +0000)
committerMatthew Dillon <dillon@dragonflybsd.org>
Mon, 8 Jan 2007 08:17:17 +0000 (08:17 +0000)
commitaaf8b91f1291a0356c8f0f18d9b1535a24ad5974
tree6e31949366c4e4a95c96047c475ca13060c2d6e7
parent4e7c41c549d873c60943035447ac04c4d30ad100
The signal return code was trying to access user mode addresses
directly, which doesn't work when the user process is in an entirely
different vmspace.  Use copyin() instead.

Assign SIGQUIT (^\) on the console to cause a virtual kernel to enter
its internal db> debugger.

Quickly hack a callout() based poller for console input so the console
works (sorta).

Allow a kernel environment to specified as an option in the form
-e name=value:name=value:...

NULL-out the pmap self-mapping cache when a pmap is destroyed.
sys/platform/vkernel/i386/cpu_regs.c
sys/platform/vkernel/i386/exception.c
sys/platform/vkernel/i386/trap.c
sys/platform/vkernel/platform/console.c
sys/platform/vkernel/platform/init.c
sys/platform/vkernel/platform/pmap.c