From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from lists.ozlabs.org (lists.ozlabs.org [112.213.38.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 488CBCCA489 for ; Tue, 26 Jul 2022 11:10:48 +0000 (UTC) Received: from boromir.ozlabs.org (localhost [IPv6:::1]) by lists.ozlabs.org (Postfix) with ESMTP id 4LsZ2t60fpz3c46 for ; Tue, 26 Jul 2022 21:10:46 +1000 (AEST) Authentication-Results: lists.ozlabs.org; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20201202 header.b=D6sUQ7Ak; dkim-atps=neutral Authentication-Results: lists.ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=kernel.org (client-ip=139.178.84.217; helo=dfw.source.kernel.org; envelope-from=pali@kernel.org; receiver=) Authentication-Results: lists.ozlabs.org; dkim=pass (2048-bit key; unprotected) header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20201202 header.b=D6sUQ7Ak; dkim-atps=neutral Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 4LsZ290YRlz2xmj for ; Tue, 26 Jul 2022 21:10:08 +1000 (AEST) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id E708D61298; Tue, 26 Jul 2022 11:10:04 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id F05C8C341C0; Tue, 26 Jul 2022 11:10:03 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1658833804; bh=WbKliBFXTxrgN6Cv+1JYUylkWk7EhU/4UIHhcTfvc+w=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=D6sUQ7AkRhrj3O9TXl462M8zzz/Jmn+VdLMYNCYl1Kb+8MAqQRzJXP7KkkU6Y5Z+F tyF223QpdJ80Dc4iKMaHoOySOkNMhJupURDnuUc4+qJOPIKQ/GcBo9e0b19zvVC5Ng s6owfbQPjXGwLS3x/8IVqw30UF8zdCcdzzyabB5bvanssQBBekLR38YZWN2SvPnObo hccladLLxbFOw0cgXwEeNHDwKjzCKbAl+uR1uHUzQznaJpIgAHGu08UkyMZGeWfhKO EfCXPCz2a/9yMhv0hei+69+0jh1g1HnyeQ6FLIn71BbyMxQglQMmqntQIRn1RQ4gut BVzexJu46i3PQ== Received: by pali.im (Postfix) id 3281782D; Tue, 26 Jul 2022 13:10:01 +0200 (CEST) Date: Tue, 26 Jul 2022 13:10:01 +0200 From: Pali =?utf-8?B?Um9ow6Fy?= To: Michael Ellerman Subject: Re: [PATCH 5/5] powerpc/pci: Add config option for using all 256 PCI buses Message-ID: <20220726111001.a2upqf5m5welcla6@pali> References: <20220706104308.5390-1-pali@kernel.org> <20220706104308.5390-6-pali@kernel.org> <20220721222145.rzgthbwoselx2l43@pali> <875yjkb0ht.fsf@mpe.ellerman.id.au> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <875yjkb0ht.fsf@mpe.ellerman.id.au> User-Agent: NeoMutt/20180716 X-BeenThere: linuxppc-dev@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Nick Child , linux-kernel@vger.kernel.org, Bjorn Helgaas , =?utf-8?Q?C=C3=A9dric?= Le Goater , linux-pci@vger.kernel.org, Paul Mackerras , linuxppc-dev@lists.ozlabs.org Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Sender: "Linuxppc-dev" On Tuesday 26 July 2022 21:02:22 Michael Ellerman wrote: > Pali Rohár writes: > > On Wednesday 06 July 2022 12:43:08 Pali Rohár wrote: > >> By default on PPC32 are PCI bus numbers unique across all PCI domains. > >> So system could have only 256 PCI buses independently of available > >> PCI domains. > >> > >> This is due to filling DT property pci-OF-bus-map which does not reflect > >> multi-domain setup. > >> > >> On all powerpc platforms except chrp and powermac there is no DT property > >> pci-OF-bus-map anymore and therefore it is possible on non-chrp/powermac > >> platforms to avoid this limitation of maximal number of 256 PCI buses in > >> system even on multi-domain setup. > >> > >> But avoiding this limitation would mean that all PCI and PCIe devices would > >> be present on completely different BDF addresses as every PCI domain starts > >> numbering PCI bueses from zero (instead of the last bus number of previous > >> enumerated PCI domain). Such change could break existing software which > >> expects fixed PCI bus numbers. > >> > >> So add a new config option CONFIG_PPC_PCI_BUS_NUM_DOMAIN_DEPENDENT which > >> enables this change. By default it is disabled. It cause that initial value > >> of hose->first_busno is zero. > >> > >> Signed-off-by: Pali Rohár > >> --- > >> arch/powerpc/Kconfig | 11 +++++++++++ > >> arch/powerpc/kernel/pci_32.c | 6 ++++++ > >> 2 files changed, 17 insertions(+) > >> > >> diff --git a/arch/powerpc/Kconfig b/arch/powerpc/Kconfig > >> index be68c1f02b79..f66084bc1dfe 100644 > >> --- a/arch/powerpc/Kconfig > >> +++ b/arch/powerpc/Kconfig > >> @@ -370,6 +370,17 @@ config PPC_DCR > >> depends on PPC_DCR_NATIVE || PPC_DCR_MMIO > >> default y > >> > >> +config PPC_PCI_BUS_NUM_DOMAIN_DEPENDENT > >> + depends on PPC32 > >> + depends on !PPC_PMAC && !PPC_CHRP > >> + bool "Assign PCI bus numbers from zero individually for each PCI domain" > >> + help > >> + By default on PPC32 were PCI bus numbers unique across all PCI domains. > >> + So system could have only 256 PCI buses independently of available > >> + PCI domains. When this option is enabled then PCI bus numbers are > >> + PCI domain dependent and each PCI controller on own domain can have > >> + 256 PCI buses, like it is on other Linux architectures. > >> + > > > > What do you think, would it be possible to set default value of this > > option to enabled? > > My preference would be to not have the option at all, just make it the > default behaviour. Every new CONFIG option adds more combinations that > need testing, or more likely don't get well tested. > > But I don't have a good feel for what could break if we turn it on, so > honestly I don't really know. > > Also I do most of my 32-bit testing on pmacs, which are not affected by > the change. It is because this change is incompatible with deprecated pci-OF-bus-map which pmac uses. I do not have any pmac box for testing or development, so I let this part as is. If one day pci-OF-bus-map would be possible to disable on pmac then this pci bus number change can be enabled also for pmac. > So I'll probably take the series as-is, and then we can do some more > widespread testing and possibly flip the default to enabled, and then > maybe remove the option entirely in future. > > cheers I have tested it on P2020 board with 3 PCIe devices, each on own bus where each bus is connected to different PCIe controller / domain and it works correctly. Every PCIe device is on bus 1 bus but on different domains.