Hello,

a few quick questions:

What exactly makes a "microhypervisor" different from an ordinary microkernel? I see how the term hypervisor makes sense for something like xen that cannot really be used sensibly by "stand-alone" applications, but looking at your spec it looks just like a (quite nice) microkernel.

How is capability revocation implemented? Are there any bounds on the execution time? If not, how are arbitrarily long kernel paths scheduled? (obviously an atomic interrupt-style kernel is not viable then ...)

Is there any support for asynchronous IPC?

Regards,
Tom


Reply via email to