Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752191AbdF3SrQ (ORCPT ); Fri, 30 Jun 2017 14:47:16 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:36254 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751072AbdF3SrP (ORCPT ); Fri, 30 Jun 2017 14:47:15 -0400 Date: Fri, 30 Jun 2017 20:46:39 +0200 (CEST) From: Thomas Gleixner To: Linus Torvalds cc: Andi Kleen , Yinghai Lu , Stephane Eranian , "H. Peter Anvin" , Ingo Molnar , Peter Zijlstra , Borislav Petkov , Linux Kernel Mailing List , Bjorn Helgaas , Matthew Wilcox , Ivan Kokshaysky , "linux-tip-commits@vger.kernel.org" Subject: Re: [tip:x86/platform] x86/PCI/mmcfg: Switch to ECAM config mode if possible In-Reply-To: Message-ID: References: <20170316215057.452220163@linutronix.de> <20170630031849.GP23705@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: 510 Lines: 14 On Fri, 30 Jun 2017, Linus Torvalds wrote: > So use the "enhanced" one for stuff above the 256-byte limit. Not for > basic probing. The probing itself uses type1 unconditionally. It just switches over when mmcfg is the default and no other quirk has been applied. Nevertheless I zap that commit in question. The rest of the series is still valid and does not affect that. The main goal of distangling the stuff from the global PCI lock and avoiding pointless nested locking is still reached. Thanks, tglx