Messages in this thread | | | Date | Wed, 24 May 2006 10:05:05 -0700 | From | Rajesh Shah <> | Subject | Re: AMD 8131 MSI quirk called too late, bus_flags not inherited ? |
| |
On Wed, May 24, 2006 at 07:59:58PM +0300, Michael S. Tsirkin wrote: > > Offtopic, something I wanted to bring up with respect to MSI, > but never had the time to debug: > > If I do > > pci_enable_msix, pci_disable_msix > > then later > > pci_enable_msi > > on the same device fails with the following message: > PCI: 0000:08:00.0: Can't enable MSI. Device already has MSI-X vectors assigned > > This is not something new - has been happening since forever. > Looks like not all MSI-X vectors get properly unassigned by pci_disable_msix. > Yes, this has been reported by others too. I've been looking at MSI code recently to fix an unrelated problem, and noticed that the code has policies about vector reservation that prevent what you're trying to do. I'm planning to clean up the MSI code shortly (patches out hopefully by next week), and will remove such policies since many people are trying to do this.
thanks, Rajesh - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |