Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757197AbYA2Osu (ORCPT ); Tue, 29 Jan 2008 09:48:50 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753113AbYA2Osi (ORCPT ); Tue, 29 Jan 2008 09:48:38 -0500 Received: from pentafluge.infradead.org ([213.146.154.40]:37891 "EHLO pentafluge.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752947AbYA2Osh (ORCPT ); Tue, 29 Jan 2008 09:48:37 -0500 Date: Tue, 29 Jan 2008 06:47:24 -0800 From: Arjan van de Ven To: tcamuso@redhat.com Cc: Greg KH , Matthew Wilcox , Grant Grundler , Loic Prylli , Adrian Bunk , Linus Torvalds , Benjamin Herrenschmidt , Ivan Kokshaysky , Greg KH , linux-kernel@vger.kernel.org, Jeff Garzik , linux-pci@atrey.karlin.mff.cuni.cz, Martin Mares Subject: Re: [Patch v2] Make PCI extended config space (MMCONFIG) a driver opt-in Message-ID: <20080129064724.0f7e91e5@laptopd505.fenrus.org> In-Reply-To: <479F34E6.40806@redhat.com> References: <20080114225225.GQ18741@parisc-linux.org> <20080114230448.GL9847@does.not.exist> <478CD8A5.5090608@myri.com> <20080115174643.GB28238@kroah.com> <20080115175641.GE18741@parisc-linux.org> <20080119165809.GB11553@colo.lackof.org> <479E1FA6.1030708@redhat.com> <20080128204431.GA15227@kroah.com> <20080128190505.5f5b1ccc@laptopd505.fenrus.org> <20080129031804.GF20198@parisc-linux.org> <20080129131955.GC10761@kroah.com> <479F34E6.40806@redhat.com> Organization: Intel X-Mailer: Claws Mail 3.2.0 (GTK+ 2.12.3; i386-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-SRS-Rewrite: SMTP reverse-path rewritten from by pentafluge.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1869 Lines: 53 On Tue, 29 Jan 2008 09:15:02 -0500 Tony Camuso wrote: > Greg KH wrote: > > On Mon, Jan 28, 2008 at 08:18:04PM -0700, Matthew Wilcox wrote: > >> I'm more optimistic because we've so severely restricted the use of > >> mmconf after these patches that it's unlikely to cause problems. > >> I also hear Vista is now using mmconf, so fewer implementations > >> are going to be buggy at this point. > > > > Hahahaha, oh, that's a good one... > > > > But what about the thousands of implementations out there that are > > buggy? > > > > I'm with Arjan here, I'm very skeptical. > > > > Matthew, with Arjan's patch, is anything that currently works now > > broken? Why do you feel it is somehow "wrong"? > > > > thanks, > > > > greg k-h > > Greg, > > The problem with Arjan's patch, if I understand it correctly, is that > it requires drivers to make a call to access extended PCI config > space. > > And, IIRC, Arjan's patch encumbers drivers for all arch's, even those > that have no MMCONFIG problems. > > The patches proposed by Loic, Ivan, Matthew, and myself, all address > the problem in an x86-specific manner that is transparent to the > drivers. this is not quite correct; the patches from Loic, Ivan, Matthew and you are for a different problem statement. Your patch problem statement is "need to fix mmconfig", my patch problem statement is "need to not make users who don't need it suffer". These are orthogonal problems. -- If you want to reach me at my work email, use arjan@linux.intel.com For development, discussion and tips for power savings, visit http://www.lesswatts.org -- 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/