Some quickies while I'm thinking about it.
Since we'll have to virtualize ring0 kernel code, it's
simple to detect idle code such as:
jmp -2
-or-
hlt
... or for that matter, maybe even guest specific OS calls that
call an idler function. So maybe if we detect when the
guest doesn't have anything useful to do and is burning
CPU cycles until the next clock tick, we can suspend
running the monitor/guest until the next time event
is supposed to occur, and then resume from there,
adding that amount of time to the time delivery framework.
Between this, and being able to let the host swap out some
pages, we should be able to trim down the footprint that
FreeMWare leaves on a system, when nothing is going on
in the guest.
-Kevin
