* Kenni Lund (kenni@xxxxxxx) wrote: > 2010/3/31 Alexander Graf <agraf@xxxxxxx>: > > The easiest thing coming to mind is to unplug the ivtv card for now. It's really only to verify that the patch does something useful :-). > > This was not sufficient. Same issue with the ivtv card unplugged...if > I interpret the content of /proc/interrupt correctly, the USB PCI > cards uses 4 IRQs and out of these three IRQs are still shared with > other components. > > The card uses IRQ 16, 18, 19, 20: > pci-stub 0000:02:01.0: PCI INT B -> GSI 18 (level, low) -> IRQ 18 > pci-stub 0000:02:01.1: PCI INT C -> GSI 16 (level, low) -> IRQ 16 > pci-stub 0000:02:01.2: PCI INT D -> GSI 20 (level, low) -> IRQ 20 > pci-stub 0000:02:01.3: PCI INT A -> GSI 19 (level, low) -> IRQ 19 > > Only IRQ 20 gets "kvm_assigned_intx_device" after > unbinding+binding+qemu-kvm launch: What is your qemu command line? It's acting as if function .2 (one of the ochi controllers) is generating the interrupt rather than .3 (the ehci controller). And indeed, there is no handler to ack that interrupt (just the likely on-board uhci one). before: 19: 0 0 0 0 IO-APIC-fasteoi ehci_hcd:usb3, uhci_hcd:usb9 20: 0 0 0 0 IO-APIC-fasteoi ohci_hcd:usb12 after: 19: 75010 73438 76479 75074 IO-APIC-fasteoi uhci_hcd:usb9 20: 0 0 0 0 IO-APIC-fasteoi kvm_assigned_intx_device Can you unbind uhci_hcd:usb9 and then give both .2 and .3 to the guest? thanks, -chris -- 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
