On 2015/9/30 20:44, Joerg Roedel wrote: > On Wed, Sep 30, 2015 at 03:45:39PM +0800, Jiang Liu wrote: >> So we need to figure out why we got irq number 0 after enabling >> MSI for AMD IOMMU device. The only hint I got is that iommu driver just >> grabbing the PCI device without providing a PCI device driver for IOMMU >> PCI device, we have solved a similar case for eata driver. So could you >> please help to apply this debug patch to gather more info and send me >> /proc/interrupts? > > I think I have an idea on how dev->irq got 0 after pci_enable_msi(). The > PCI probe code calls pcibios_alloc_irq() and after a failed probe it calls > pcibios_free_irq(), which sets dev->irq to 0. > The AMD IOMMU driver does not register a pci_driver for itself, it just > doesn't make sense for it. But the PCI device containing the IOMMU gets > probed later, which fails because there is no driver for it. So the > following call to pcibios_free_irq() clears dev->irq, so that it is 0 on > the next resume. Does that make sense?
Thanks Joerg, that makes sense. If some driver tries to binding to the IOMMU device, it will trigger the scenario as you described. For example, Xen backend driver will try to probe all PCI devices if enabled. I will do more investigation tomorrow. Thanks! Gerry -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
