Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759302AbYAaF7T (ORCPT ); Thu, 31 Jan 2008 00:59:19 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751211AbYAaF7J (ORCPT ); Thu, 31 Jan 2008 00:59:09 -0500 Received: from outbound-mail-39.bluehost.com ([69.89.20.193]:54440 "HELO outbound-mail-39.bluehost.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1751061AbYAaF7I (ORCPT ); Thu, 31 Jan 2008 00:59:08 -0500 X-Greylist: delayed 397 seconds by postgrey-1.27 at vger.kernel.org; Thu, 31 Jan 2008 00:59:08 EST From: Jesse Barnes To: Greg KH Subject: Re: [Patch v2] Make PCI extended config space (MMCONFIG) a driver opt-in Date: Wed, 30 Jan 2008 21:51:12 -0800 User-Agent: KMail/1.9.6 (enterprise 0.20071204.744707) Cc: Matthew Wilcox , Arjan van de Ven , Tony Camuso , 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 References: <20080114225225.GQ18741@parisc-linux.org> <20080129031804.GF20198@parisc-linux.org> <20080129131955.GC10761@kroah.com> In-Reply-To: <20080129131955.GC10761@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200801302151.12544.jbarnes@virtuousgeek.org> X-Identified-User: {642:box128.bluehost.com:virtuous:virtuousgeek.org} {sentby:smtp auth 169.222.10.15 authed with jbarnes@virtuousgeek.org} Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1328 Lines: 32 On Tuesday 29 January 2008 05:19:55 am Greg KH wrote: > 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. Ugg, let's look at the actual data (again); I'm really not sure why people are jumping to such dire conclusions about the current state of things. AIUI we only have 3 issues so far (remember mmconfig has been enabled in -mm for a long time): 1) host bridge decode problems (disabling decode to avoid overlaps can cause some bridges to stop decoding RAM addrs, but we have a fix for that) 2) config space retry on ATI (I think willy already debunked this one?) 3) some FUD about SMM or other firmware interrupts coming in during BAR sizing while decode is disabled (this one is just pure FUD; if we want to solve it properly we need a new platform hook to disable SMM/NMI/etc. around PCI probing) What else was there? What reason do we have to think that things are so disastrous? So I really prefer willy's approach to Arjan's alternative... Jesse -- 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/