From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com> To: "Luis R. Rodriguez" <mcgrof@kernel.org> Cc: Liviu Dudau <liviu@dudau.co.uk>, Bjorn Helgaas <helgaas@kernel.org>, Liviu Dudau <Liviu.Dudau@arm.com>, "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>, Andy Lutomirski <luto@amacapital.net>, linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Wenrui Li <wenrui.li@rock-chips.com>, Gabriele Paoloni <gabriele.paoloni@huawei.com>, Catalin Marinas <catalin.marinas@arm.com>, Shawn Lin <shawn.lin@rock-chips.com>, Will Deacon <will.deacon@arm.com>, Michal Simek <michal.simek@xilinx.com>, Thierry Reding <thierry.reding@gmail.com>, Tanmay Inamdar <tinamdar@apm.com>, linux-arch@vger.kernel.org, Pratyush Anand <pratyush.anand@gmail.com>, Russell King <linux@armlinux.org.uk>, Jon Mason <jonmason@broadcom.com>, Murali Karicheri <m-karicheri2@ti.com> Subject: Re: [PATCH 02/20] PCI: fix pci_remap_iospace() remap attribute Date: Mon, 20 Mar 2017 16:19:33 +0000 [thread overview] Message-ID: <20170320161933.GD7632@red-moon> (raw) In-Reply-To: <20170317162617.GC28800@wotan.suse.de> On Fri, Mar 17, 2017 at 05:26:18PM +0100, Luis R. Rodriguez wrote: > 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. It started with this thread: http://lists.infradead.org/pipermail/linux-arm-kernel/2017-January/477353.html this series is not fixing any current issue I am aware of (but I am not keen on leaving code as-is either) hence adding a Fixes: tag is problematic. I would leave stable kernels alone for the time being. Lorenzo > > > 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
WARNING: multiple messages have this Message-ID (diff)
From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com> To: "Luis R. Rodriguez" <mcgrof@kernel.org> Cc: Liviu Dudau <liviu@dudau.co.uk>, Bjorn Helgaas <helgaas@kernel.org>, Liviu Dudau <Liviu.Dudau@arm.com>, "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>, Andy Lutomirski <luto@amacapital.net>, linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Wenrui Li <wenrui.li@rock-chips.com>, Gabriele Paoloni <gabriele.paoloni@huawei.com>, Catalin Marinas <catalin.marinas@arm.com>, Shawn Lin <shawn.lin@rock-chips.com>, Will Deacon <will.deacon@arm.com>, Michal Simek <michal.simek@xilinx.com>, Thierry Reding <thierry.reding@gmail.com>, Tanmay Inamdar <tinamdar@apm.com>, linux-arch@vger.kernel.org, Pratyush Anand <pratyush.anand@gmail.com>, Russell King <linux@armlinux.org.uk>, Jon Mason <jonmason@broadcom.com>, Murali Karicheri <m-karicheri2@ti.com>, Arnd Bergmann <arnd@arndb.de>, Bharat Kumar Gogada <bharat.kumar.gogada@xilinx.com>, Ray Jui <rjui@broadcom.com>, John Garry <john.garry@huawei.com>, Joao Pinto <Joao.Pinto@synopsys.com>, Bjorn Helgaas <bhelgaas@google.com>, Mingkai Hu <mingkai.hu@freescale.com>, Thomas Petazzoni <thomas.petazzoni@free-electrons.com>, Jingoo Han <jingoohan1@gmail.com>, linux-kernel@vger.kernel.org, Stanimir Varbanov <svarbanov@mm-sol.com>, Minghuan Lian <minghuan.Lian@freescale.com>, Zhou Wang <wangzhou1@hisilicon.com>, Roy Zang <tie-fei.zang@freescale.com> Subject: Re: [PATCH 02/20] PCI: fix pci_remap_iospace() remap attribute Date: Mon, 20 Mar 2017 16:19:33 +0000 [thread overview] Message-ID: <20170320161933.GD7632@red-moon> (raw) Message-ID: <20170320161933.ymYqWAhhGxYbT_rTCoXOOGjnILvXveNNpQrnQTE3lzA@z> (raw) In-Reply-To: <20170317162617.GC28800@wotan.suse.de> On Fri, Mar 17, 2017 at 05:26:18PM +0100, Luis R. Rodriguez wrote: > 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. It started with this thread: http://lists.infradead.org/pipermail/linux-arm-kernel/2017-January/477353.html this series is not fixing any current issue I am aware of (but I am not keen on leaving code as-is either) hence adding a Fixes: tag is problematic. I would leave stable kernels alone for the time being. Lorenzo > > > 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
next prev parent reply other threads:[~2017-03-20 16:19 UTC|newest] Thread overview: 109+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-02-27 15:14 [PATCH 00/20] PCI: fix config and I/O Address space memory mappings Lorenzo Pieralisi 2017-02-27 15:14 ` Lorenzo Pieralisi 2017-02-27 15:14 ` [PATCH 01/20] PCI: remove __weak tag from pci_remap_iospace() Lorenzo Pieralisi 2017-02-27 15:14 ` Lorenzo Pieralisi 2017-03-01 16:15 ` Arnd Bergmann 2017-03-01 16:15 ` Arnd Bergmann 2017-02-27 15:14 ` [PATCH 02/20] PCI: fix pci_remap_iospace() remap attribute Lorenzo Pieralisi 2017-02-27 15:14 ` Lorenzo Pieralisi 2017-03-16 21:48 ` Bjorn Helgaas 2017-03-16 21:48 ` Bjorn Helgaas 2017-03-17 0:33 ` Luis R. Rodriguez 2017-03-17 0:33 ` Luis R. Rodriguez 2017-03-17 10:43 ` Liviu Dudau 2017-03-17 10:43 ` Liviu Dudau 2017-03-17 16:26 ` Luis R. Rodriguez 2017-03-17 16:26 ` Luis R. Rodriguez 2017-03-20 16:19 ` Lorenzo Pieralisi [this message] 2017-03-20 16:19 ` Lorenzo Pieralisi 2017-03-20 16:06 ` Bjorn Helgaas 2017-03-20 16:06 ` Bjorn Helgaas 2017-03-20 16:26 ` Lorenzo Pieralisi 2017-03-20 16:26 ` Lorenzo Pieralisi 2017-03-20 16:38 ` Bjorn Helgaas 2017-03-20 16:38 ` Bjorn Helgaas 2017-02-27 15:14 ` [PATCH 03/20] asm-generic/io.h: add PCI config space remap interface Lorenzo Pieralisi 2017-02-27 15:14 ` Lorenzo Pieralisi 2017-03-16 21:12 ` Bjorn Helgaas 2017-03-16 21:12 ` Bjorn Helgaas 2017-03-17 0:08 ` Luis R. Rodriguez 2017-03-17 0:08 ` Luis R. Rodriguez 2017-03-20 10:22 ` John Garry 2017-03-20 10:22 ` John Garry 2017-03-20 16:27 ` Bjorn Helgaas 2017-03-20 16:27 ` Bjorn Helgaas 2017-03-20 18:45 ` Lorenzo Pieralisi 2017-03-20 18:45 ` Lorenzo Pieralisi 2017-03-22 15:04 ` Lorenzo Pieralisi 2017-03-22 15:04 ` Lorenzo Pieralisi 2017-03-22 15:15 ` Arnd Bergmann 2017-03-22 15:15 ` Arnd Bergmann 2017-03-22 16:29 ` Bjorn Helgaas 2017-03-22 16:29 ` Bjorn Helgaas 2017-02-27 15:14 ` [PATCH 04/20] ARM64: implement pci_remap_cfgspace() interface Lorenzo Pieralisi 2017-02-27 15:14 ` Lorenzo Pieralisi 2017-02-27 15:14 ` [PATCH 05/20] ARM: " Lorenzo Pieralisi 2017-02-27 15:14 ` Lorenzo Pieralisi 2017-03-20 16:43 ` Russell King - ARM Linux 2017-03-20 16:43 ` Russell King - ARM Linux 2017-03-21 15:26 ` Lorenzo Pieralisi 2017-03-21 15:26 ` Lorenzo Pieralisi 2017-03-21 16:53 ` Russell King - ARM Linux 2017-03-21 16:53 ` Russell King - ARM Linux 2017-02-27 15:14 ` [PATCH 06/20] PCI: ECAM: use pci_remap_cfgspace() to map config region Lorenzo Pieralisi 2017-02-27 15:14 ` Lorenzo Pieralisi 2017-02-27 15:14 ` [PATCH 07/20] PCI: implement Devres interface to map PCI config space Lorenzo Pieralisi 2017-02-27 15:14 ` Lorenzo Pieralisi 2017-02-28 10:43 ` Lorenzo Pieralisi 2017-02-28 10:43 ` Lorenzo Pieralisi 2017-03-01 23:54 ` Andy Shevchenko 2017-03-01 23:54 ` Andy Shevchenko 2017-03-02 12:05 ` Lorenzo Pieralisi 2017-03-02 12:05 ` Lorenzo Pieralisi 2017-03-02 12:50 ` Andy Shevchenko 2017-03-02 12:50 ` Andy Shevchenko 2017-03-02 19:24 ` Tejun Heo 2017-03-02 19:24 ` Tejun Heo 2017-03-02 20:08 ` Thierry Reding 2017-03-02 20:08 ` Thierry Reding 2017-02-27 15:14 ` [PATCH 08/20] PCI: xilinx: update PCI config space remap function Lorenzo Pieralisi 2017-02-27 15:14 ` Lorenzo Pieralisi 2017-02-27 15:14 ` [PATCH 09/20] PCI: xilinx-nwl: " Lorenzo Pieralisi 2017-02-27 15:14 ` Lorenzo Pieralisi 2017-02-27 15:14 ` [PATCH 10/20] PCI: spear13xx: " Lorenzo Pieralisi 2017-02-27 15:14 ` Lorenzo Pieralisi 2017-02-27 15:14 ` [PATCH 11/20] PCI: rockchip: " Lorenzo Pieralisi 2017-02-27 15:14 ` Lorenzo Pieralisi 2017-02-27 15:14 ` [PATCH 12/20] PCI: qcom: " Lorenzo Pieralisi 2017-02-27 15:14 ` Lorenzo Pieralisi 2017-02-27 15:14 ` [PATCH 13/20] PCI: iproc-platform: " Lorenzo Pieralisi 2017-02-27 15:14 ` Lorenzo Pieralisi 2017-02-27 21:21 ` Ray Jui 2017-02-27 21:21 ` Ray Jui 2017-02-28 10:54 ` Lorenzo Pieralisi 2017-02-28 10:54 ` Lorenzo Pieralisi 2017-02-28 17:42 ` Ray Jui 2017-02-28 17:42 ` Ray Jui 2017-02-27 15:14 ` [PATCH 14/20] PCI: hisi: " Lorenzo Pieralisi 2017-02-27 15:14 ` Lorenzo Pieralisi 2017-03-02 10:56 ` Gabriele Paoloni 2017-03-02 10:56 ` Gabriele Paoloni 2017-03-02 11:49 ` Lorenzo Pieralisi 2017-03-02 11:49 ` Lorenzo Pieralisi 2017-03-02 11:53 ` Gabriele Paoloni 2017-03-02 11:53 ` Gabriele Paoloni 2017-02-27 15:14 ` [PATCH 15/20] PCI: designware: " Lorenzo Pieralisi 2017-02-27 15:14 ` Lorenzo Pieralisi 2017-02-27 15:14 ` [PATCH 16/20] PCI: armada8k: " Lorenzo Pieralisi 2017-02-27 15:14 ` Lorenzo Pieralisi 2017-02-27 15:14 ` [PATCH 17/20] PCI: xgene: " Lorenzo Pieralisi 2017-02-27 15:14 ` Lorenzo Pieralisi 2017-02-27 15:14 ` [PATCH 18/20] PCI: tegra: " Lorenzo Pieralisi 2017-02-27 15:14 ` Lorenzo Pieralisi 2017-02-27 15:14 ` [PATCH 19/20] PCI: layerscape: " Lorenzo Pieralisi 2017-02-27 15:14 ` [PATCH 20/20] PCI: keystone-dw: " Lorenzo Pieralisi 2017-02-27 15:14 ` Lorenzo Pieralisi 2017-03-01 16:18 ` [PATCH 00/20] PCI: fix config and I/O Address space memory mappings Arnd Bergmann 2017-03-01 16:18 ` Arnd Bergmann 2017-03-02 18:00 ` Lorenzo Pieralisi 2017-03-02 18:00 ` Lorenzo Pieralisi
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20170320161933.GD7632@red-moon \ --to=lorenzo.pieralisi@arm.com \ --cc=Liviu.Dudau@arm.com \ --cc=catalin.marinas@arm.com \ --cc=gabriele.paoloni@huawei.com \ --cc=helgaas@kernel.org \ --cc=jonmason@broadcom.com \ --cc=linux-arch@vger.kernel.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-pci@vger.kernel.org \ --cc=linux@armlinux.org.uk \ --cc=liviu@dudau.co.uk \ --cc=luto@amacapital.net \ --cc=m-karicheri2@ti.com \ --cc=mcgrof@kernel.org \ --cc=michal.simek@xilinx.com \ --cc=paulmck@linux.vnet.ibm.com \ --cc=pratyush.anand@gmail.com \ --cc=shawn.lin@rock-chips.com \ --cc=thierry.reding@gmail.com \ --cc=tinamdar@apm.com \ --cc=wenrui.li@rock-chips.com \ --cc=will.deacon@arm.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).