Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751519AbdCNR4l (ORCPT ); Tue, 14 Mar 2017 13:56:41 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:43742 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750996AbdCNR4k (ORCPT ); Tue, 14 Mar 2017 13:56:40 -0400 Date: Tue, 14 Mar 2017 18:56:26 +0100 (CET) From: Thomas Gleixner To: Andi Kleen cc: Andi Kleen , bhelgaas@google.com, x86@kernel.org, linux-pci@vger.kernel.org, eranian@google.com, Peter Zijlstra , LKML Subject: Re: [PATCH 3/4] x86, pci: Add interface to force mmconfig In-Reply-To: <20170314170255.GH32070@tassilo.jf.intel.com> Message-ID: References: <20170302232104.10136-1-andi@firstfloor.org> <20170302232104.10136-3-andi@firstfloor.org> <20170314154155.GG32070@tassilo.jf.intel.com> <20170314170255.GH32070@tassilo.jf.intel.com> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 781 Lines: 22 On Tue, 14 Mar 2017, Andi Kleen wrote: > The other option is to simply make it unconditional. That would > be even simpler, but it is a bit more risky. Hmm, I suppose may > be worth trying to find out what Windows uses. If they get away > with MMCONFIG everywhere we should be too. >From the PCIe spec: The PCI 3.0 compatible Configuration Space can be accessed using either the mechanism defined in the PCI Local Bus Specification or the PCI Express Enhanced Configuration Access Mechanism (ECAM) described later in this section. Accesses made using either access mechanism are equivalent. The PCI Express Extended Configuration Space can only be accessed by using the ECAM. The 1.0 spec has a similar wording (s/3.0/2.3). Definitely the best way to go. Thanks, tglx