Messages in this thread | | | From | "Ravinandan Arakali" <> | Subject | RE: MSI-X support on AMD 8132 platforms ? | Date | Tue, 16 May 2006 11:44:59 -0700 |
| |
Hi Petr, Thanks for the suggestion. What you pointed out was the source of the problem. After enabling the MSI-to-HTInterrupts(the value at offset 0xF6), I now see interrupts and can ping in both MSI and MSI-X modes.
Ravi
-----Original Message----- From: Petr Vandrovec [mailto:vandrove@vc.cvut.cz] Sent: Tuesday, May 16, 2006 8:01 AM To: Andi Kleen Cc: ravinandan.arakali@neterion.com; Peter. Phan; Leonid Grossman; linux-kernel@vger.kernel.org Subject: Re: MSI-X support on AMD 8132 platforms ?
Andi Kleen wrote: > "Ravinandan Arakali" <ravinandan.arakali@neterion.com> writes: > > >>I was wondering if anybody has got MSI-X going on AMD 8132 platforms. >>Our network card and driver support MSI-X and the combination works >>fine on IA64 and xeon platforms. But on the 8132, the MSI-X vectors are >>assigned(pci_enable_msix succeeds) but no interrupts get generated. > > > See erratum #78 in the AMD 8132 Specification update. > It doesn't support the MSI capability and there are no plans to fix that. > > AFAIK the only way to get MSI on Opteron is on PCI Express.
I do not think that erratum #78 is related to this - it is related to tunnel itself generating MSI - which is not needed in this case.
>>Note that with a different OS, MSI-X does work on 8132. > > Are you sure?
Can you provide 'lspci -vvvxxx' output from AMD8132 bridge? (esp. bytes 0xF4-0xFF from config space of 1022:7458 devices) By default dword at 0xF4 is 0xA8000008, disabling MSI/MSI-X mapping -> hypertransport interrupts. Changing this to 0xA8010008 should enable this translation (iff qword at 0xF8 is 0x0000FEE00000), allowing MSI to work on respective secondary/subordinate busses. Unfortunately kernel ignores these HT capabilities... Petr
- 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/
| |