Gregory Haskins wrote: > (assuming that hasn't happened already?) > > One thing that would make my life easier going forward would be if we could > separate out the interrupt related state from the [gs]et_sregs() calls. What > I propose is that we make two new calls (say [gs]et_pic). For "level-0" mode > this will be saving/restoring the 256-bit "userint" array. For other modes, > it will be saving whatever is relevant for the APIC (registers, etc). The > userspace code would be aware of which mode it is operating under anyway, > since it has to enable the feature. >
While we can slip in such a change to mainline, we're committed to supporting the current ABI for Fedora 7, so there's not much point. However, I don't see an issue. You could specify that when the feature is enabled, the irq state in get/set sregs is ignored, and the new functions are to be used. -- error compiling committee.c: too many arguments to function ------------------------------------------------------------------------- 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