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 X-Spam-Level: X-Spam-Status: No, score=-7.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 288BAC4338F for ; Thu, 19 Aug 2021 15:48:48 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 0640D610A6 for ; Thu, 19 Aug 2021 15:48:48 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S240657AbhHSPtR (ORCPT ); Thu, 19 Aug 2021 11:49:17 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34190 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235645AbhHSPtG (ORCPT ); Thu, 19 Aug 2021 11:49:06 -0400 Received: from mail-il1-x12b.google.com (mail-il1-x12b.google.com [IPv6:2607:f8b0:4864:20::12b]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 24DCBC061575; Thu, 19 Aug 2021 08:48:30 -0700 (PDT) Received: by mail-il1-x12b.google.com with SMTP id f15so6419479ilk.4; Thu, 19 Aug 2021 08:48:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=1XLarHIwSltc8JzGiLc6RNqTtH7ZzdM7gO/rhwWjhvA=; b=r/PFK0f5g1h3iNeVtG4snJF+KC48zZHcYCI84FO17uz8H20Aw09ixwoI/EYFXkj4ys w0xkg72L8/LKn6+Hsn51N/mlAh58jLtOjsOMd+jK3YOuN4ykgEFQsK4L60oHtFvBo/l3 mnMPWgAbbgdzGPyVKC57FFMOnwbpN2Gm4F0usY3COQZzLu4l+2MbmyngWsm7NfkKaYtI exHtanNjlEpg2ooe6vp6hJfmI90AwwXBdET443Kym3ELr/c0rDYj39+vuRGyrsQUUHwT qq8RPsflRY6eQ96bv0Oqmyz8eukNlnV7xkKf8jjfJ5GOrzIXdIkbs0m8kYLWPd+gbrEi mXyA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=1XLarHIwSltc8JzGiLc6RNqTtH7ZzdM7gO/rhwWjhvA=; b=gLNrQXw0nO6aBi2kHrE9DTdt6VIFxV8c4587ahvXEn0PtZFe+31B/3B1lFGb0e4knA wWxn1+b7RlLpM4ZJKOzKy/1UMaUF7/gVa4Vg06gjJR5qeOIK9NtX0/MqYhARSfJpfli8 pBjDfTr9yeSaZXlO9t/CHvbwZ28SYqHNcWobzNwuPUPvpcY/sQF0baGh6kuzZZBxxHDV ld+uxDqKPQsV8lmKdUKiFYTeo32si8yHD7XUSQT3siMlkpFQaqygg/Y5KPoye37kY5pw Uc+2+c6LZjJlSyh7bsILjdFgRiDLD2kSJMFMABEcqoHD22WdAcJTwZ/Z722jpHziS+cJ KoAQ== X-Gm-Message-State: AOAM5331CFHhRZUOu31ymImpHVyKCjQG/Si/W/QHul0SaHULWAOqWcWp RAvrQKU1GVM3g1XJlgBTIEI= X-Google-Smtp-Source: ABdhPJxf1Iuq2VjFkgmnwcK558JcDv6YWHuAZODF3dmKo/CLmewJHtCzfHU4BDfB/JOzSkzE4daXSw== X-Received: by 2002:a92:ad12:: with SMTP id w18mr10056613ilh.3.1629388108869; Thu, 19 Aug 2021 08:48:28 -0700 (PDT) Received: from auth2-smtp.messagingengine.com (auth2-smtp.messagingengine.com. [66.111.4.228]) by smtp.gmail.com with ESMTPSA id m184sm1815314ioa.17.2021.08.19.08.48.27 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 19 Aug 2021 08:48:28 -0700 (PDT) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailauth.nyi.internal (Postfix) with ESMTP id 43C2C27C005C; Thu, 19 Aug 2021 11:48:26 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Thu, 19 Aug 2021 11:48:27 -0400 X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrleejgdeludcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpeffhffvuffkfhggtggujgesthdtredttddtvdenucfhrhhomhepuehoqhhunhcu hfgvnhhguceosghoqhhunhdrfhgvnhhgsehgmhgrihhlrdgtohhmqeenucggtffrrghtth gvrhhnpeevieejtdfhieejfeduheehvdevgedugeethefggfdtvdeutdevgeetvddvfeeg tdenucffohhmrghinhepkhgvrhhnvghlrdhorhhgnecuvehluhhsthgvrhfuihiivgeptd enucfrrghrrghmpehmrghilhhfrhhomhepsghoqhhunhdomhgvshhmthhprghuthhhphgv rhhsohhnrghlihhthidqieelvdeghedtieegqddujeejkeehheehvddqsghoqhhunhdrfh gvnhhgpeepghhmrghilhdrtghomhesfhhigihmvgdrnhgrmhgv X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 19 Aug 2021 11:48:25 -0400 (EDT) Date: Thu, 19 Aug 2021 23:47:52 +0800 From: Boqun Feng To: Lorenzo Pieralisi Cc: Catalin Marinas , Will Deacon , Bjorn Helgaas , Arnd Bergmann , Marc Zyngier , "K. Y. Srinivasan" , Haiyang Zhang , Stephen Hemminger , Wei Liu , Dexuan Cui , Rob Herring , Krzysztof =?utf-8?Q?Wilczy=C5=84ski?= , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-hyperv@vger.kernel.org, linux-pci@vger.kernel.org, Sunil Muthuswamy , Mike Rapoport Subject: Re: [PATCH v6 0/8] PCI: hv: Support host bridge probing on ARM64 Message-ID: References: <20210726180657.142727-1-boqun.feng@gmail.com> <20210819141758.GA27305@lpieralisi> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210819141758.GA27305@lpieralisi> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Aug 19, 2021 at 03:17:58PM +0100, Lorenzo Pieralisi wrote: > On Tue, Jul 27, 2021 at 02:06:49AM +0800, Boqun Feng wrote: > > Hi, > > > > This is the v6 for the preparation of virtual PCI support on Hyper-V > > ARM64, Previous versions: > > > > v1: https://lore.kernel.org/lkml/20210319161956.2838291-1-boqun.feng@gmail.com/ > > v2: https://lore.kernel.org/lkml/20210503144635.2297386-1-boqun.feng@gmail.com/ > > v3: https://lore.kernel.org/lkml/20210609163211.3467449-1-boqun.feng@gmail.com/ > > v4: https://lore.kernel.org/lkml/20210714102737.198432-1-boqun.feng@gmail.com/ > > v5: https://lore.kernel.org/lkml/20210720134429.511541-1-boqun.feng@gmail.com/ > > > > Changes since last version: > > > > * Rebase to 5.14-rc3 > > > > * Comment fixes as suggested by Bjorn. > > > > The basic problem we need to resolve is that ARM64 is an arch with > > PCI_DOMAINS_GENERIC=y, so the bus sysdata is pci_config_window. However, > > Hyper-V PCI provides a paravirtualized PCI interface, so there is no > > actual pci_config_window for a PCI host bridge, so no information can be > > retrieve from the pci_config_window of a Hyper-V virtual PCI bus. Also > > there is no corresponding ACPI device for the Hyper-V PCI root bridge, > > which introduces a special case when trying to find the ACPI device from > > the sysdata (see patch #3). > > > > With this patchset, we could enable the virtual PCI on Hyper-V ARM64 > > guest with other code under development. > > > > Comments and suggestions are welcome. > > > > Regards, > > Boqun > > > > Arnd Bergmann (1): > > PCI: hv: Generify PCI probing > > > > Boqun Feng (7): > > PCI: Introduce domain_nr in pci_host_bridge > > PCI: Support populating MSI domains of root buses via bridges > > arm64: PCI: Restructure pcibios_root_bridge_prepare() > > arm64: PCI: Support root bridge preparation for Hyper-V > > PCI: hv: Set ->domain_nr of pci_host_bridge at probing time > > PCI: hv: Set up MSI domain at bridge probing time > > PCI: hv: Turn on the host bridge probing on ARM64 > > > > arch/arm64/kernel/pci.c | 29 +++++++--- > > drivers/pci/controller/pci-hyperv.c | 86 +++++++++++++++++------------ > > drivers/pci/probe.c | 12 +++- > > include/linux/pci.h | 11 ++++ > > 4 files changed, 93 insertions(+), 45 deletions(-) > > If we take this series via the PCI tree we'd need Catalin/Will ACKs on > patches 3-4. > Got it. > I need some time to look into [1] (thanks for that). > > Without [1] patch 8 is ugly, that's no news. The question is whether > it is worth waiting for a kernel cycle to integrate [1] into this series > or not. > > Is it really a problem if we postpone this series for another kernel > cycle so that we can look into it ? > Well, it's definitely better for me that we can have it in 5.15-rc1 ;-), because it's a dependency for Hyper-V virtual PCI support on ARM64 and we plan to send the rest of work in 5.15 cycle. And I can just base on hyperv-next for the rest of the work if this is in 5.15-rc1. But yes, it's not really a problem, since this one still needs to work with other patches to support virtual PCI on ARM64 Hyper-V. In fact, I personally don't think [1] is better than patch 8 (plus patch 3 & 4): playing with ->private seems dangerous and not very helpful on readiblity, but I agree that we should explore every potential solution, and that's why I send [1]. Regards, Boqun > [1] https://lore.kernel.org/lkml/20210811153619.88922-1-boqun.feng@gmail.com/ 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 X-Spam-Level: X-Spam-Status: No, score=-5.7 required=3.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED, DKIM_SIGNED,DKIM_VALID,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 7E8B6C4338F for ; Thu, 19 Aug 2021 15:50:38 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 4E250610D2 for ; Thu, 19 Aug 2021 15:50:38 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 4E250610D2 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=fja7jsmJ4CBeMuZtcfgz+TI7xzNDho4cqIgR4RK9Tks=; b=lDkyQSJo0IhuGM D93zVSyh9OMd74U/5FNHm1Xk7sZO6Aw2ewWckxG4RK96HxDf8edN+e6sOzXSMFgBZ3yTcMeBVSdKD J1YLPcP8KXn5kL2+owrKDJ9C0WWYu2P0mjXX/NTQUrrWNQknugjJ/oZaYTN8bReIeSc3kxilj1M7n X8dTM5isC2A/+tX2YxWryT+X0TNv2AOA0z94uQ77vB55C2Ga8FZAOvVf7lfxA9Y9DJAVTxsYXjIxz gtmDU/VbYzKpatK/niN8HnvFGTNdYmhytwDO06CWgAMsYH0qBfhYIbNcsSIxBzwYaJ5FZGsFW47Iu DoP/O+Kbc4Dkqmiy9wqg==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1mGkHS-008sDD-KP; Thu, 19 Aug 2021 15:48:34 +0000 Received: from mail-il1-x135.google.com ([2607:f8b0:4864:20::135]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1mGkHO-008sC6-Mv for linux-arm-kernel@lists.infradead.org; Thu, 19 Aug 2021 15:48:32 +0000 Received: by mail-il1-x135.google.com with SMTP id v2so6399460ilg.12 for ; Thu, 19 Aug 2021 08:48:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=1XLarHIwSltc8JzGiLc6RNqTtH7ZzdM7gO/rhwWjhvA=; b=r/PFK0f5g1h3iNeVtG4snJF+KC48zZHcYCI84FO17uz8H20Aw09ixwoI/EYFXkj4ys w0xkg72L8/LKn6+Hsn51N/mlAh58jLtOjsOMd+jK3YOuN4ykgEFQsK4L60oHtFvBo/l3 mnMPWgAbbgdzGPyVKC57FFMOnwbpN2Gm4F0usY3COQZzLu4l+2MbmyngWsm7NfkKaYtI exHtanNjlEpg2ooe6vp6hJfmI90AwwXBdET443Kym3ELr/c0rDYj39+vuRGyrsQUUHwT qq8RPsflRY6eQ96bv0Oqmyz8eukNlnV7xkKf8jjfJ5GOrzIXdIkbs0m8kYLWPd+gbrEi mXyA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=1XLarHIwSltc8JzGiLc6RNqTtH7ZzdM7gO/rhwWjhvA=; b=byhbRQ45/fZ11GFJ5B9DzBTYrtWegAHIauHrpG3CVdFDv5Px7sp8acjDjrdxxTYqrh 88aXd80XCv+hfMhZHNEJlH8WSPtBRg45Qrm6rOTJybMNGWmNVFHYdpNcqo9qMBX8G8t4 wt4W+CFpBu2c705Hy/iBMeDY3xc5RoJxerK/K+HoxkAlOadNKSm0I920mEL1oAn3aRZ3 JjxRsCaQnXAk/0z6fWoH8SrOBK5ocSavisP4oN2hGusBVOUnDwCLZweR689zaoc9bXfo zYUaAIeCwfpPZwrZW+2e9l8J1vgVESEpkRQcVd8lJP/d029UdNGT17G4f9VT6ahcvblH 95ag== X-Gm-Message-State: AOAM53094hIY7Dva+NQPKHHkJFhPLW5Db6OaQ0KA8W+3/n/3imVRyywz AafTR7IFlctjmpvp98cgkh4= X-Google-Smtp-Source: ABdhPJxf1Iuq2VjFkgmnwcK558JcDv6YWHuAZODF3dmKo/CLmewJHtCzfHU4BDfB/JOzSkzE4daXSw== X-Received: by 2002:a92:ad12:: with SMTP id w18mr10056613ilh.3.1629388108869; Thu, 19 Aug 2021 08:48:28 -0700 (PDT) Received: from auth2-smtp.messagingengine.com (auth2-smtp.messagingengine.com. [66.111.4.228]) by smtp.gmail.com with ESMTPSA id m184sm1815314ioa.17.2021.08.19.08.48.27 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 19 Aug 2021 08:48:28 -0700 (PDT) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailauth.nyi.internal (Postfix) with ESMTP id 43C2C27C005C; Thu, 19 Aug 2021 11:48:26 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Thu, 19 Aug 2021 11:48:27 -0400 X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrleejgdeludcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpeffhffvuffkfhggtggujgesthdtredttddtvdenucfhrhhomhepuehoqhhunhcu hfgvnhhguceosghoqhhunhdrfhgvnhhgsehgmhgrihhlrdgtohhmqeenucggtffrrghtth gvrhhnpeevieejtdfhieejfeduheehvdevgedugeethefggfdtvdeutdevgeetvddvfeeg tdenucffohhmrghinhepkhgvrhhnvghlrdhorhhgnecuvehluhhsthgvrhfuihiivgeptd enucfrrghrrghmpehmrghilhhfrhhomhepsghoqhhunhdomhgvshhmthhprghuthhhphgv rhhsohhnrghlihhthidqieelvdeghedtieegqddujeejkeehheehvddqsghoqhhunhdrfh gvnhhgpeepghhmrghilhdrtghomhesfhhigihmvgdrnhgrmhgv X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 19 Aug 2021 11:48:25 -0400 (EDT) Date: Thu, 19 Aug 2021 23:47:52 +0800 From: Boqun Feng To: Lorenzo Pieralisi Cc: Catalin Marinas , Will Deacon , Bjorn Helgaas , Arnd Bergmann , Marc Zyngier , "K. Y. Srinivasan" , Haiyang Zhang , Stephen Hemminger , Wei Liu , Dexuan Cui , Rob Herring , Krzysztof =?utf-8?Q?Wilczy=C5=84ski?= , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-hyperv@vger.kernel.org, linux-pci@vger.kernel.org, Sunil Muthuswamy , Mike Rapoport Subject: Re: [PATCH v6 0/8] PCI: hv: Support host bridge probing on ARM64 Message-ID: References: <20210726180657.142727-1-boqun.feng@gmail.com> <20210819141758.GA27305@lpieralisi> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20210819141758.GA27305@lpieralisi> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20210819_084830_799372_21065691 X-CRM114-Status: GOOD ( 35.35 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Thu, Aug 19, 2021 at 03:17:58PM +0100, Lorenzo Pieralisi wrote: > On Tue, Jul 27, 2021 at 02:06:49AM +0800, Boqun Feng wrote: > > Hi, > > > > This is the v6 for the preparation of virtual PCI support on Hyper-V > > ARM64, Previous versions: > > > > v1: https://lore.kernel.org/lkml/20210319161956.2838291-1-boqun.feng@gmail.com/ > > v2: https://lore.kernel.org/lkml/20210503144635.2297386-1-boqun.feng@gmail.com/ > > v3: https://lore.kernel.org/lkml/20210609163211.3467449-1-boqun.feng@gmail.com/ > > v4: https://lore.kernel.org/lkml/20210714102737.198432-1-boqun.feng@gmail.com/ > > v5: https://lore.kernel.org/lkml/20210720134429.511541-1-boqun.feng@gmail.com/ > > > > Changes since last version: > > > > * Rebase to 5.14-rc3 > > > > * Comment fixes as suggested by Bjorn. > > > > The basic problem we need to resolve is that ARM64 is an arch with > > PCI_DOMAINS_GENERIC=y, so the bus sysdata is pci_config_window. However, > > Hyper-V PCI provides a paravirtualized PCI interface, so there is no > > actual pci_config_window for a PCI host bridge, so no information can be > > retrieve from the pci_config_window of a Hyper-V virtual PCI bus. Also > > there is no corresponding ACPI device for the Hyper-V PCI root bridge, > > which introduces a special case when trying to find the ACPI device from > > the sysdata (see patch #3). > > > > With this patchset, we could enable the virtual PCI on Hyper-V ARM64 > > guest with other code under development. > > > > Comments and suggestions are welcome. > > > > Regards, > > Boqun > > > > Arnd Bergmann (1): > > PCI: hv: Generify PCI probing > > > > Boqun Feng (7): > > PCI: Introduce domain_nr in pci_host_bridge > > PCI: Support populating MSI domains of root buses via bridges > > arm64: PCI: Restructure pcibios_root_bridge_prepare() > > arm64: PCI: Support root bridge preparation for Hyper-V > > PCI: hv: Set ->domain_nr of pci_host_bridge at probing time > > PCI: hv: Set up MSI domain at bridge probing time > > PCI: hv: Turn on the host bridge probing on ARM64 > > > > arch/arm64/kernel/pci.c | 29 +++++++--- > > drivers/pci/controller/pci-hyperv.c | 86 +++++++++++++++++------------ > > drivers/pci/probe.c | 12 +++- > > include/linux/pci.h | 11 ++++ > > 4 files changed, 93 insertions(+), 45 deletions(-) > > If we take this series via the PCI tree we'd need Catalin/Will ACKs on > patches 3-4. > Got it. > I need some time to look into [1] (thanks for that). > > Without [1] patch 8 is ugly, that's no news. The question is whether > it is worth waiting for a kernel cycle to integrate [1] into this series > or not. > > Is it really a problem if we postpone this series for another kernel > cycle so that we can look into it ? > Well, it's definitely better for me that we can have it in 5.15-rc1 ;-), because it's a dependency for Hyper-V virtual PCI support on ARM64 and we plan to send the rest of work in 5.15 cycle. And I can just base on hyperv-next for the rest of the work if this is in 5.15-rc1. But yes, it's not really a problem, since this one still needs to work with other patches to support virtual PCI on ARM64 Hyper-V. In fact, I personally don't think [1] is better than patch 8 (plus patch 3 & 4): playing with ->private seems dangerous and not very helpful on readiblity, but I agree that we should explore every potential solution, and that's why I send [1]. Regards, Boqun > [1] https://lore.kernel.org/lkml/20210811153619.88922-1-boqun.feng@gmail.com/ _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel