public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Max Krasnyansky <maxk@qualcomm.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	tom.l.nguyen@intel.com, Greg KH <gregkh@suse.de>
Subject: Re: PCI MSI: the new interrupt routing headache
Date: Thu, 17 Nov 2005 11:07:26 -0800	[thread overview]
Message-ID: <437CD4EE.4060807@qualcomm.com> (raw)
In-Reply-To: <437C18AF.7050508@pobox.com>

Hi Jeff,
> 
> I just got SATA working on Marvell.  After fixing a bunch of issues in 
> the driver, the final issue was lack of interrupts.  Disabling 
> CONFIG_PCI_MSI solved that, and suddenly the driver was working quite 
> nicely.
> 
> The general problem is that pci_enable_msi() is not failing, on systems 
> that do not support MSI.  This leads to Infiniband, tg3, and other 
> drivers working around this problem by including an MSI-interrupts-work 
> test during probe.
> 
> Perhaps its because I like leading edge stuff, and am playing with 
> drivers for PCI MSI hardware, but it seems like I am running into this 
> pci_enable_msi()-doesnt-fail problem more and more frequently.  First 
> tg3, then AHCI, now sata_mv.
> 
> What needs to be done, to detect working PCI message signalled 
> interrupts such that pci_enable_msi() fails properly?
It fails correctly when MSI quirk is enabled. I had the same problems
on AMD 8131 based machine with 2.6.11 kernel. E1000 was enabling MSI and
not getting any interrupts. Later (.13 I think) MSI quirk was introduced for
8131 chipset and everything started working (without having to hack E1000
that is).
May be you should just add your platform to the PCI quirks list ?

Max

  reply	other threads:[~2005-11-17 19:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-17  5:44 PCI MSI: the new interrupt routing headache Jeff Garzik
2005-11-17 19:07 ` Max Krasnyansky [this message]
2005-11-18 20:52 ` Roland Dreier

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=437CD4EE.4060807@qualcomm.com \
    --to=maxk@qualcomm.com \
    --cc=gregkh@suse.de \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tom.l.nguyen@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox