All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Maule <maule@sgi.com>
To: Greg KH <greg@kroah.com>
Cc: "Miller, Mike (OS Dev)" <Mike.Miller@hp.com>,
	linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
	"Patterson, Andrew D (Linux R&D)" <andrew.patterson@hp.com>
Subject: Re: FW: MSI-X on 2.6.15
Date: Mon, 30 Jan 2006 13:09:37 -0600	[thread overview]
Message-ID: <20060130190937.GB31945@sgi.com> (raw)
In-Reply-To: <20060130173852.GA16259@kroah.com>

As Ashok Raj has already responded, there was support for APIC-based MSI[-X]
on ia64 before my patches.  I personally do not know if it worked or not, my
suspicion is that it didn't get much airtime due to MSI being off by default
until somewhat recently.

I believe MSI was working on zx1 after my patch, so I suspect it worked there
before my patch as well.  I can't speak to MSI-X.

Mike, is your driver capable of MSI (vs. MSI-X)?  As a datapoint, could you
try that?

Mark

On Mon, Jan 30, 2006 at 09:38:52AM -0800, Greg KH wrote:
> On Mon, Jan 30, 2006 at 10:33:50AM -0600, Miller, Mike (OS Dev) wrote:
> > Greg KH,
> > We have the same results on 2.6.15, the MSI-X table is all zeroes. See
> > below. Any ideas of what to do do next? The driver works on x86_64. Is
> > there any thing extra I need to do on ia64?
> 
> ia64 didn't really have msi support before the latest -mm kernel, right
> Mark?
> 
> > Andrew, can you try 2.6.16-rc1 and/or the rc1-git4 kernels?
> 
> How about the -mm kernel?
> 
> thanks,
> 
> greg k-h

  parent reply	other threads:[~2006-01-30 19:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-30 16:33 FW: MSI-X on 2.6.15 Miller, Mike (OS Dev)
2006-01-30 16:33 ` Miller, Mike (OS Dev)
2006-01-30 17:38 ` Greg KH
2006-01-30 17:56   ` Ashok Raj
2006-01-30 19:09   ` Mark Maule [this message]
2006-01-30 21:33   ` Roland Dreier
  -- strict thread matches above, loose matches on Subject: below --
2006-01-30 20:18 Miller, Mike (OS Dev)
2006-01-30 20:18 ` 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=20060130190937.GB31945@sgi.com \
    --to=maule@sgi.com \
    --cc=Mike.Miller@hp.com \
    --cc=andrew.patterson@hp.com \
    --cc=greg@kroah.com \
    --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 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.