On Wed, 2012-08-08 at 11:52 +0300, Avi Kivity wrote: > > So for now I'm just doing my own version of CREATE_IRQCHIP to create it > > and KVM_INTERRUPT to trigger the various interrupts. None of the mapping > > stuff (which we really don't need). > > You mean KVM_IRQ_LINE. KVM_INTERRUPT is a synchronous vcpu ioctl. Yes, sorry, brain and fingers not agreeing :-) > > That's a bit of a problem vs. some of the code qemu-side such as in > > virtio-pci which does seem to be written around the model exposed by the > > x86 stuff and relies on doing such mappings so I think we'll have to > > butcher some of that. > > Can you elaborate? virtio-pci is pci-centric, there should be nothing > x86 specific there. The kvm_irqchip_add_msi_route & co is a problem, it more/less dives into the x86/ia64 specific routing stuff at a generic level, I'll have to hook things up differently in qemu I suspect. Not a huge deal, we can sort it out. Cheers, Ben. -- 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
