linux-kernel - Re: [PATCH] pci: enable MSI on 8132

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 18 Feb 2009 14:18:33 -0600
From:	James Bottomley <James.Bottomley@...senPartnership.com>
To:	Jeff Garzik <jeff@...zik.org>
Cc:	Yinghai Lu <yinghai@...nel.org>,
	Andrew Morton <akpm@...ux-foundation.org>, david@...g.hm,
	Matthew Wilcox <matthew@....cx>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	linux-scsi@...r.kernel.org, DL-MPTFusionLinux@....com,
	linux-pci@...r.kernel.org
Subject: Re: [PATCH] pci: enable MSI on 8132

On Wed, 2009-02-18 at 15:12 -0500, Jeff Garzik wrote:
> James Bottomley wrote:
> > Like I said, I'm happy to have MSI completely disabled until LSI wants
> > to comment, so no ... only the PCI quirk fix.  The true fix is to have
> > the drivers participate in dynamic testing of MSI IRQ routing, but I've
> > somewhat lost sight of that.
> 
> That's not really a fix at all, just additional, unneeded overhead for 
> 99% of users.  We don't need our drivers bloated with self-check code 
> for all the components in our various computer chips...

So you think the current per driver variably named parameter to turn off
MSI is better?  Especially as most of the users who trip across a
platform having MSI problems don't even know that the storage failure is
caused by MSI, let alone how to find the parameter to fix the problem.

James


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