linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Miller, Mike (OS Dev)" <Mike.Miller@hp.com>
To: <linux-kernel@vger.kernel.org>, <linux-scsi@vger.kernel.org>,
	<linux-ia64@vger.kernel.org>
Subject: Problems with MSI-X on ia64
Date: Thu, 26 Jan 2006 11:14:22 -0600	[thread overview]
Message-ID: <D4CFB69C345C394284E4B78B876C1CF10B848090@cceexc23.americas.cpqcorp.net> (raw)

Hello,
Has anyone tested MSI-X on ia64 based platforms? 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. On Intel x86_64
platforms the table contains valid data and everything works as
expected.

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.

Thanks,
mikem

             reply	other threads:[~2006-01-26 17:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-26 17:14 Miller, Mike (OS Dev) [this message]
2006-01-26 17:24 ` Problems with MSI-X on ia64 Mark Maule
2006-01-26 20:24 ` Grant Grundler
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
2006-06-01  6:35   ` Grant Grundler
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=D4CFB69C345C394284E4B78B876C1CF10B848090@cceexc23.americas.cpqcorp.net \
    --to=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;
as well as URLs for NNTP newsgroup(s).