Question:

Right now, the ioctl() dumps back to the user code whenever
the monitor switches back to the host context.  However,
shouldn't the standard action be that the ioctl() code
(switch to monitor, check why it switched back) should run
in a loop, and that it only breaks out of it when an event
requires to be handled by the user code ?  The way it is now
we get a user<-->kernel switch and back on every quantum
(slow).

Ulrich mentioned that linux multitasks cooperatively in
kernel mode.  Ulrich, is calling schedule() inside the
loop enough to make it go right ?  If it is I'll go put
that in the code :)

Ramon

Reply via email to