From: Grant Grundler <iod00d@hp.com>
To: "Miller, Mike (OS Dev)" <Mike.Miller@hp.com>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-ia64@vger.kernel.org
Subject: Re: Problems with MSI-X on ia64
Date: Thu, 26 Jan 2006 12:24:47 -0800 [thread overview]
Message-ID: <20060126202447.GB15440@esmail.cup.hp.com> (raw)
In-Reply-To: <D4CFB69C345C394284E4B78B876C1CF10B848090@cceexc23.americas.cpqcorp.net>
On Thu, Jan 26, 2006 at 11:14:22AM -0600, Miller, Mike (OS Dev) wrote:
> Hello,
> Has anyone tested MSI-X on ia64 based platforms?
IIRC, Martine Silberman did some of the developement for
ia64 support. At least she provided the original documentation
for 2.6.4 kernel. So this is mostly not new code.
http://www.ussg.iu.edu/hypermail/linux/kernel/0402.2/1543.html
I've also posted 2.6.10 tg3 patch to enable MSI:
http://www.gelato.unsw.edu.au/archives/linux-ia64/0503/13332.html
I've been using MSI-X on ia64 with OpenIB for over a year.
My guess is that was also starting with 2.6.10.
Here's current output with 2.6.15:
grundler@gsyprf3:/usr/src/linux-2.6.15$ fgrep MSI /proc/interrupts
70: 1067582561 0 PCI-MSI-X ib_mthca (comp)
71: 10 0 PCI-MSI-X ib_mthca (async)
72: 41279 0 PCI-MSI-X ib_mthca (cmd)
> We're using a 2.6.9 variant and a cciss driver with MSI/MSI-X support.
> The kernel has MSI enabled. On ia64 the MSI-X table is all zeroes.
Could you post the debug output you've collected so far?
> On Intel x86_64 platforms the table contains valid data and
> everything works as expected.
It should look similar for ia64 since both use 0xfeeXXXXX
Processor Interrupt Block address and similar intr vectors.
> If I understand how this works the Linux kernel is supposed to program
> up the table based on the HW platform. I can't find anything in the ia64
> code that does this. For x86_64 and i386 it looks like the magic address
> is
>
> #define APIC_DEFAULT_BASE 0xfee00000
>
> Anybody know why this isn't defined for ia64? Any answers, input, or
> flames are appreciated.
APIC_DEAFULT_BASE isn't used. See
fgrep MSI_ADDRESS_HEADER drivers/pci/*
drivers/pci/msi.c: dest_id = (MSI_ADDRESS_HEADER << MSI_ADDRESS_HEADER_SHIFT);
drivers/pci/msi.h:#define MSI_ADDRESS_HEADER 0xfee
drivers/pci/msi.h:#define MSI_ADDRESS_HEADER_SHIFT 12
drivers/pci/msi.h:#define MSI_ADDRESS_HEADER_MASK 0xfff000
This is one of the things that Mark Maule/SGI needs to change
to support MSI on SN2.
grant
next prev parent reply other threads:[~2006-01-26 20:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-26 17:14 Problems with MSI-X on ia64 Miller, Mike (OS Dev)
2006-01-26 17:24 ` Mark Maule
2006-01-26 20:24 ` Grant Grundler [this message]
2006-02-17 7:58 ` Grant Grundler
2006-02-17 8:46 ` Chris Wedgwood
2006-02-17 14:11 ` Matthew Wilcox
2006-02-17 16:36 ` Grant Grundler
2006-02-17 19:10 ` Chris Wedgwood
-- strict thread matches above, loose matches on Subject: below --
2006-01-26 20:37 Miller, Mike (OS Dev)
2006-01-27 4:37 ` Greg KH
2006-01-27 15:34 Miller, Mike (OS Dev)
2006-02-17 19:52 Luck, Tony
2006-02-17 20:04 ` Grant Grundler
2006-02-17 20:21 ` Roland Dreier
2006-02-21 20:21 Miller, Mike (OS Dev)
2006-02-25 16:23 ` Grant Grundler
2006-02-27 18:36 Miller, Mike (OS Dev)
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=20060126202447.GB15440@esmail.cup.hp.com \
--to=iod00d@hp.com \
--cc=Mike.Miller@hp.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox