> Hope it should work like the following [Please correct me if I'm > wrong]: > - 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. > The line is temporarily jammed but not disabled - note_interrupt() > will not consider > our irq unhandled and won't disable it. > btw, if I'm not mistaken only after bad 99900/100000 the irq is > disabled. > - 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. > > Maybe it's better to code it first then send RFC.
Definitely. We've already agreed that it's correct for the (rare, unfortunately) non shared scenario. Let's see how much do we have to bend reality to fit once it's in code form. -- Ors. ------------------------------------------------------------------------- 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
