> - Make the device the last irqaction in the list > - Our dummy handler will always return IRQ_HANDLED in case any other > previous > irqaction did not return such. It will also issue the timer and mask > the irq in this case.
Ok > btw, if I'm not mistaken only after bad 99900/100000 the irq is > disabled. (and with GIT providing that they occurred in a short time period) > - If the timer pops before the guest acks the irq, the timer handler > will > ack the irq and unmask it. The timer's job is only to prevent > deadlocks. Ok I see what you are doing. It's either inspired or insane and I am not quite sure which of the two. I agree it should work although may cause performance crunches now and then and will also need care getting the locking right. Alan ------------------------------------------------------------------------- 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
