Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752182AbXL0LrZ (ORCPT ); Thu, 27 Dec 2007 06:47:25 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751363AbXL0LrS (ORCPT ); Thu, 27 Dec 2007 06:47:18 -0500 Received: from srv5.dvmed.net ([207.36.208.214]:45925 "EHLO mail.dvmed.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751356AbXL0LrR (ORCPT ); Thu, 27 Dec 2007 06:47:17 -0500 Message-ID: <4773908E.80600@garzik.org> Date: Thu, 27 Dec 2007 06:46:22 -0500 From: Jeff Garzik User-Agent: Thunderbird 2.0.0.9 (X11/20071115) MIME-Version: 1.0 To: Linus Torvalds CC: Ivan Kokshaysky , Loic Prylli , Arjan van de Ven , linux-kernel@vger.kernel.org, gregkh@suse.de, linux-pci@atrey.karlin.mff.cuni.cz, Benjamin Herrenschmidt Subject: Re: [patch] Make MMCONFIG space (extended PCI config space) a driver opt-in issue References: <476D1D16.5090703@garzik.org> <20071222064719.73fdd9a4@laptopd505.fenrus.org> <476DB95F.3090801@garzik.org> <476DDFEE.3010009@garzik.org> <476DE98F.2010009@garzik.org> <476DF1A6.3060900@myri.com> <476DF5BE.5030004@garzik.org> <20071223110337.GA25441@jurassic.park.msu.ru> <476F6047.50100@garzik.org> In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: -4.4 (----) X-Spam-Report: SpamAssassin version 3.2.3 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 Content-Length: 964 Lines: 25 Linus Torvalds wrote: > Well, the *current* behaviour as far as setup is concerned is > unacceptable. But yes, longer term, we should be able to just have quirk > entries for saying "enable mmconfig because I know it's safe", except we > should not enable them until after the core PCI probing has completed. IMO that should be an arch decision, buried somewhere in arch/x86. If other arches implement extended config space sanely -- and possibly via some arch-specific means that is /not/ mmconfig -- then they should be able to make an arch decision that extended PCI config space accesses Just Work(tm). For such arches, pci_enable_ext_cfg_space(pdev) would be a no-op, always returning success. Jeff -- 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/