From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751243AbdCQQ2p (ORCPT ); Fri, 17 Mar 2017 12:28:45 -0400 Received: from mx2.suse.de ([195.135.220.15]:55994 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751107AbdCQQ2n (ORCPT ); Fri, 17 Mar 2017 12:28:43 -0400 Date: Fri, 17 Mar 2017 17:26:18 +0100 From: "Luis R. Rodriguez" To: Liviu Dudau Cc: "Luis R. Rodriguez" , Bjorn Helgaas , Liviu Dudau , Lorenzo Pieralisi , "Paul E. McKenney" , Andy Lutomirski , linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Wenrui Li , Gabriele Paoloni , Catalin Marinas , Shawn Lin , Will Deacon , Michal Simek , Thierry Reding , Tanmay Inamdar , linux-arch@vger.kernel.org, Pratyush Anand , Russell King , Jon Mason , Murali Karicheri , Arnd Bergmann , Bharat Kumar Gogada , Ray Jui , John Garry , Joao Pinto , Bjorn Helgaas , Mingkai Hu , Thomas Petazzoni , Jingoo Han , linux-kernel@vger.kernel.org, Stanimir Varbanov , Minghuan Lian , Zhou Wang , Roy Zang Subject: Re: [PATCH 02/20] PCI: fix pci_remap_iospace() remap attribute Message-ID: <20170317162617.GC28800@wotan.suse.de> References: <20170227151436.18698-1-lorenzo.pieralisi@arm.com> <20170227151436.18698-3-lorenzo.pieralisi@arm.com> <20170316214844.GA17769@bhelgaas-glaptop.roam.corp.google.com> <20170317003321.GB28800@wotan.suse.de> <20170317104339.GD24830@bart.dudau.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170317104339.GD24830@bart.dudau.co.uk> User-Agent: Mutt/1.6.0 (2016-04-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Mar 17, 2017 at 10:43:39AM +0000, Liviu Dudau wrote: > On Fri, Mar 17, 2017 at 01:33:21AM +0100, Luis R. Rodriguez wrote: > > a) should we then use a Fixes tag for this patch ? > > I'm not aware of issues being reported, but Lorenzo might have more info on this. Lorenzo ? If not what exactly made you discover this ? If it is a fix, and only ARM64 is implicated, seems like a worthy change to consider for stable for the sake of stable ARM64 kernels. But, that would leave the PCI config space without a simple 1 liner fix too -- so maybe its not worth it. Distributions wanting to support ARM64 however would like to carry these changes, so some annotations such as Fixes should help. > > b) it does not seem clear what the semantics for pgprot_device() or even > > pgprot_noncached(). Can you add some ? > > > > 8b921acfeffdb ("PCI: Add pci_remap_iospace() to map bus I/O resources") > > > > Also this patch claims archs can override this call alone, as its __weak. > > So is the right thing to do to change pci_remap_iospace() to pgprot_noncached() > > or is it for archs to add their own pci_remap_iospace()? If so why ? Without > > proper semantics defined for these helpers this is all fuzzy. > > That was the initial intention, to let arches / platforms overwrite the whole > pci_remap_iospace(). I guess the reality is that no one needs to overwrite it except > for the AArch64 quirk, so probably easier to remove the __weak and fix the attributes for arm64. Sounds much more reasonable to me. Luis