Ingo Molnar wrote: > * Avi Kivity <[EMAIL PROTECTED]> wrote: > > any 'cut' of the interface to allow both qemu and KVM generate vectors > is unnecessary (and harmful) complexity. The interface cut should be > at > the 'pin' level, with Qemu raising a signal on a pin and lowering a > signal on a pin, but otherwise not dealing with IRQ routing and IRQ > vectors. > Actually, current Qemu device is not well designed to support this behavior, it will call pic_set_irq even if the 'pin' state doesn't change for some reason. In Xen, we ever tracked the 'pin' state in Qemu too so that only 'raising' and 'lowering' a signal will inform VMM like you mentioned. But this logic is removed later on at cleanup.
Thx, Eddie ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
