From: Jeff Garzik <jgarzik@pobox.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: tom.l.nguyen@intel.com, Greg KH <gregkh@suse.de>
Subject: PCI MSI: the new interrupt routing headache
Date: Thu, 17 Nov 2005 00:44:15 -0500 [thread overview]
Message-ID: <437C18AF.7050508@pobox.com> (raw)
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?
Thanks,
Jeff
next reply other threads:[~2005-11-17 5:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-17 5:44 Jeff Garzik [this message]
2005-11-17 19:07 ` PCI MSI: the new interrupt routing headache Max Krasnyansky
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=437C18AF.7050508@pobox.com \
--to=jgarzik@pobox.com \
--cc=gregkh@suse.de \
--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