On Thu, May 21, 2009 at 02:53:14PM +0100, Paul Brook wrote: > > > which is a trivial wrapper around stl_phys. > > > > OK, but I'm adding another level of indirection in the middle, > > to allow us to tie in a kvm backend. > > kvm has no business messing with the PCI device code.
Yes it has :) 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. -- MST -- 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
