> * the kprocdev framework. all i/o into devip, devfs, and devdraw > is marshalled and handed off to a kproc running in a different > pthread, so that blocking i/o won't block the cpu0 pthread, > which is the only one that can run vx32. this means that > all i/o gets copied one extra time inside the kernel.
why can only one thread run vx32? - erik
