From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754415AbZBRUPn (ORCPT ); Wed, 18 Feb 2009 15:15:43 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752180AbZBRUPc (ORCPT ); Wed, 18 Feb 2009 15:15:32 -0500 Received: from srv5.dvmed.net ([207.36.208.214]:49205 "EHLO mail.dvmed.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751756AbZBRUPb (ORCPT ); Wed, 18 Feb 2009 15:15:31 -0500 Message-ID: <499C6BC9.6010706@garzik.org> Date: Wed, 18 Feb 2009 15:12:57 -0500 From: Jeff Garzik User-Agent: Thunderbird 2.0.0.19 (X11/20090105) MIME-Version: 1.0 To: James Bottomley CC: Yinghai Lu , Andrew Morton , david@lang.hm, Matthew Wilcox , Jesse Barnes , linux-kernel , linux-scsi@vger.kernel.org, DL-MPTFusionLinux@lsi.com, linux-pci@vger.kernel.org Subject: Re: [PATCH] pci: enable MSI on 8132 References: <499B46B2.5040601@kernel.org> <499B6BF7.9090300@kernel.org> <499B724A.2040408@kernel.org> <499B774C.5010705@kernel.org> <499B9129.50104@kernel.org> <20090218122137.GJ16841@parisc-linux.org> <20090218100448.7f7c5b86.akpm@linux-foundation.org> <1234982285.3225.42.camel@localhost.localdomain> <499C5CAD.1070404@kernel.org> <1234984495.3225.48.camel@localhost.localdomain> In-Reply-To: <1234984495.3225.48.camel@localhost.localdomain> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: -4.4 (----) X-Spam-Report: SpamAssassin version 3.2.5 on srv5.dvmed.net summary: Content analysis details: (-4.4 points, 5.0 required) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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... Jeff