Message-ID: <437C18AF.7050508@pobox.com>
Date: Thu, 17 Nov 2005 00:44:15 -0500
From: Jeff Garzik <jgarzik@pobox.com>
User-Agent: Mozilla Thunderbird 1.0.7-1.1.fc4 (X11/20050929)
MIME-Version: 1.0
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
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1073
Lines: 30


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


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/