Michael S. Tsirkin wrote: > kvm needs data on MSI entries: that's the interface > current kernel exposes for injecting these interrupts. > > I think we also need to support in-kernel devices which > would inject MSI interrupt directly from kernel. > For these, kvm would need to know when mask bit changes > and give us info on pending bit. > > That's a fair amount of PCI specific code in kvm My plan is to get rid of it. The mask stuff need not be pci specific. -- error compiling committee.c: too many arguments to function _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/virtualization
