On Wednesday 18 February 2009 19:29:28 Avi Kivity wrote: > Sheng Yang wrote: > > On Wednesday 18 February 2009 19:00:53 Avi Kivity wrote: > >> Sheng Yang wrote: > >>> We have to handle more than one interrupt with one handler for MSI-X. > >>> So we need a bitmap to track the triggered interrupts. > >> > >> Can you explain why? > > > > Or how can we know which interrupt happened? Current we scheduled the > > work later, and no more irq information available at that time. > > We can have a work_struct per interrupt, or we can set a flag in the > msix array that the interrupt is pending. As I know, work_struct itself don't take any data. And host MSI-X array is a type of msix_entry* which is used for pci_enable_msix. But modifying type of guest msix entries should be OK. I will try. -- regards Yang, Sheng -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html