From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751389AbdCOCYc (ORCPT ); Tue, 14 Mar 2017 22:24:32 -0400 Received: from one.firstfloor.org ([193.170.194.197]:53997 "EHLO one.firstfloor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751052AbdCOCYT (ORCPT ); Tue, 14 Mar 2017 22:24:19 -0400 Date: Tue, 14 Mar 2017 19:24:14 -0700 From: Andi Kleen To: Bjorn Helgaas Cc: Thomas Gleixner , Andi Kleen , 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 Message-ID: <20170315022414.GC14380@two.firstfloor.org> 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> <20170314194720.GD26264@bhelgaas-glaptop.roam.corp.google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170314194720.GD26264@bhelgaas-glaptop.roam.corp.google.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > I agree that it should be fairly safe to do ECAM/MMCONFIG without > locking. Can we handle the decision part by adding a "lockless" bit > to struct pci_ops? Old ops don't mention that bit, so it will be > initialized to zero and we'll do locking as today. ECAM/MMCONFIG ops > can set it and we can skip the locking. That's what my other patch already did. -Andi