Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932207AbWJPAPh (ORCPT ); Sun, 15 Oct 2006 20:15:37 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751283AbWJPAPg (ORCPT ); Sun, 15 Oct 2006 20:15:36 -0400 Received: from smtp.osdl.org ([65.172.181.4]:22208 "EHLO smtp.osdl.org") by vger.kernel.org with ESMTP id S1751281AbWJPAPf (ORCPT ); Sun, 15 Oct 2006 20:15:35 -0400 Date: Sun, 15 Oct 2006 17:15:24 -0700 From: Andrew Morton To: Paul Mackerras Cc: Matthew Wilcox , Alan Cox , David Brownell , val_henson@linux.intel.com, netdev@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz, linux-kernel@vger.kernel.org, gregkh@suse.de Subject: Re: [Bulk] Re: [PATCH 1/2] [PCI] Check that MWI bit really did get set Message-Id: <20061015171524.b85f97b7.akpm@osdl.org> In-Reply-To: <17714.52121.962807.781244@cargo.ozlabs.ibm.com> References: <1160161519800-git-send-email-matthew@wil.cx> <20061013214135.8fbc9f04.akpm@osdl.org> <20061014140249.GL11633@parisc-linux.org> <20061014134855.b66d7e65.akpm@osdl.org> <20061015032000.GP11633@parisc-linux.org> <20061015070809.978C714552@adsl-69-226-248-13.dsl.pltn13.pacbell.net> <1160922082.5732.51.camel@localhost.localdomain> <20061015135756.GD22289@parisc-linux.org> <20061015104544.5de31608.akpm@osdl.org> <17714.52121.962807.781244@cargo.ozlabs.ibm.com> X-Mailer: Sylpheed version 2.2.7 (GTK+ 2.8.17; x86_64-unknown-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 810 Lines: 20 On Mon, 16 Oct 2006 10:00:25 +1000 Paul Mackerras wrote: > Andrew Morton writes: > > > If the drivers doesn't care and if it makes no difference to performance > > then just delete the call to pci_set_mwi(). > > > > But if MWI _does_ make a difference to performance then we should tell > > someone that it isn't working rather than silently misbehaving? > > That sounds like we need a printk inside pci_set_mwi then, rather than > adding a printk to every single caller. > I think so, yes. That's a good solution to a lot of these things. - 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/