All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vandrovec <vandrove@vc.cvut.cz>
To: Andi Kleen <ak@suse.de>
Cc: ravinandan.arakali@neterion.com,
	"Peter. Phan" <peter.phan@neterion.com>,
	Leonid Grossman <Leonid.Grossman@neterion.com>,
	linux-kernel@vger.kernel.org
Subject: Re: MSI-X support on AMD 8132 platforms ?
Date: Tue, 16 May 2006 17:01:10 +0200	[thread overview]
Message-ID: <4469E936.1020804@vc.cvut.cz> (raw)
In-Reply-To: <p73hd3r5czi.fsf@bragg.suse.de>

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


  reply	other threads:[~2006-05-16 15:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-04 23:16 pci_enable_msix throws up error Ravinandan Arakali
2006-05-15 17:44 ` MSI-X support on AMD 8132 platforms ? Ravinandan Arakali
2006-05-15 19:01   ` Andi Kleen
2006-05-16 15:01     ` Petr Vandrovec [this message]
2006-05-16 18:44       ` Ravinandan Arakali

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4469E936.1020804@vc.cvut.cz \
    --to=vandrove@vc.cvut.cz \
    --cc=Leonid.Grossman@neterion.com \
    --cc=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter.phan@neterion.com \
    --cc=ravinandan.arakali@neterion.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.