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
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
