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=-11.0 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=unavailable 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 54CE1C4338F for ; Thu, 19 Aug 2021 14:20:14 +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 11FAD61100 for ; Thu, 19 Aug 2021 14:20:14 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 11FAD61100 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=arm.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=vNlIDdbQak6aA0LZD3vv5J1QNnhcESUkoFCDNwQSRcM=; b=iuXF9NxC+mv8Q6 Zib0nT1LZEzBmUMNiYKW41dRGpotJ8DrPou5Ru6N438MNzdv3Yh0WdrzLnKg6WczJgPPJAt4/7fOZ tVgtG8O/wrt4AIeWzbo0Pw9OdJj3d4vPErAWj0oXGtdelggUV8pIDZ0FIeoixbUVa+AWqRBcshh4S aE2gY8EjVwAB4tfX7unmEbE4u1yULYs5jWhqJ2HMXdjli012ewDJEFBqjoVsUN5yzLFuYVEwlx2rg B2rTazM4Eb0xTSZMAob9l3Aalniqjygg8BvZy75mtI+C3x4q6vHE8LDwbq8mRjwVtLC9pCAWbcTUP HM41gauMCZeS3c5NZJmw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1mGis3-008d3b-CP; Thu, 19 Aug 2021 14:18:15 +0000 Received: from foss.arm.com ([217.140.110.172]) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1mGirx-008d1h-8t for linux-arm-kernel@lists.infradead.org; Thu, 19 Aug 2021 14:18:11 +0000 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 9B0EC106F; Thu, 19 Aug 2021 07:18:06 -0700 (PDT) Received: from lpieralisi (e121166-lin.cambridge.arm.com [10.1.196.255]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 178653F66F; Thu, 19 Aug 2021 07:18:03 -0700 (PDT) Date: Thu, 19 Aug 2021 15:17:58 +0100 From: Lorenzo Pieralisi To: Boqun Feng , Catalin Marinas , Will Deacon Cc: 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: <20210819141758.GA27305@lpieralisi> References: <20210726180657.142727-1-boqun.feng@gmail.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20210726180657.142727-1-boqun.feng@gmail.com> User-Agent: Mutt/1.9.4 (2018-02-28) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20210819_071809_478456_18ECFC3C X-CRM114-Status: GOOD ( 22.71 ) 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 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. 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 ? [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