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 19:14:55 +0000
From:	James Bottomley <James.Bottomley@...senPartnership.com>
To:	Yinghai Lu <yinghai@...nel.org>
Cc:	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 11:08 -0800, Yinghai Lu wrote:
> James Bottomley wrote:
> > On Wed, 2009-02-18 at 10:04 -0800, Andrew Morton wrote:
> > 
> >> Do we not need mpt-fix-enable-lsi-sas-to-use-msi-as-default.patch as
> >> well, to fix this regression?
> > 
> > No ... it's a separate issue.  MSI was enabled for fusion SAS in 2.6.26;
> > the problem msi patch which the above corrects actually has the effect
> > of disabling MSI for fusion and went into 2.6.29-rc2, which isn't a
> > kernel that's been tested here.
> > 
> 
> so for 2.6.26, 27, 28 need pci-enable-msi-on-8132.patch

I'm a bit lost with the names, but if that's the PCI quirk fix, then yes

> 2.6.29 need pci-enable-msi-on-8132.patch and mpt-fix-enable-lsi-sas-to-use-msi-as-default.patch

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.

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/