>>> On Tue, Apr 24, 2007 at 5:17 AM, in message <[EMAIL PROTECTED]>, Avi Kivity <[EMAIL PROTECTED]> wrote: > Gregory Haskins wrote: > >> Are there any other userspace sleeps that we need to handle (e.g. maybe > AIO)? If so, one way to handle this is to mark the exportable state of the > VCPU such that userspace can tell if interrupts are pending. However, I'm > not really sure if this is the best way to do it or if it can be easily done > in a way that doesn't break ABI compatiblity. Please advise. >> > > The ABI can be extended by adding fields to struct kvm_vcpu_run and an > extension check to indicate their availability.
Cool. I was not aware of that capability. In that case, I think the reasonable thing to do is just that (extend to allow "pending" status). If the new userspace (which will implicitly understand the presence of an in-kernel APIC) needs to know, it can be coded to check this state. -Greg ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
