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.gnu.org (lists.gnu.org [209.51.188.17]) (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 E58BFC02192 for ; Wed, 5 Feb 2025 10:45:04 +0000 (UTC) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tfctK-0006Sn-64; Wed, 05 Feb 2025 05:44:22 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tfctF-0006RK-Pd; Wed, 05 Feb 2025 05:44:17 -0500 Received: from frasgout.his.huawei.com ([185.176.79.56]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tfctB-0005zA-SY; Wed, 05 Feb 2025 05:44:16 -0500 Received: from mail.maildlp.com (unknown [172.18.186.231]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4YnxcR1jRmz6D8X1; Wed, 5 Feb 2025 18:41:43 +0800 (CST) Received: from frapeml500008.china.huawei.com (unknown [7.182.85.71]) by mail.maildlp.com (Postfix) with ESMTPS id B0895140CB1; Wed, 5 Feb 2025 18:43:58 +0800 (CST) Received: from frapeml500008.china.huawei.com (7.182.85.71) by frapeml500008.china.huawei.com (7.182.85.71) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.39; Wed, 5 Feb 2025 11:43:53 +0100 Received: from frapeml500008.china.huawei.com ([7.182.85.71]) by frapeml500008.china.huawei.com ([7.182.85.71]) with mapi id 15.01.2507.039; Wed, 5 Feb 2025 11:43:53 +0100 To: Nicolin Chen , Eric Auger CC: "ddutile@redhat.com" , Peter Maydell , Jason Gunthorpe , =?iso-8859-1?Q?Daniel_P=2E_Berrang=E9?= , "qemu-arm@nongnu.org" , "qemu-devel@nongnu.org" , Linuxarm , "Wangzhou (B)" , jiangkunkun , "Jonathan Cameron" , "zhangfei.gao@linaro.org" Subject: RE: [RFC PATCH 0/5] hw/arm/virt: Add support for user-creatable nested SMMUv3 Thread-Topic: [RFC PATCH 0/5] hw/arm/virt: Add support for user-creatable nested SMMUv3 Thread-Index: AQHbMeB0+Q5BEZc9JkeH/U6Jz+dF4rLkOMCAgAAM2QCAAAz2gIAEhqeggCVVAYCAI176AIAE12cAgAGBGYCAAGn5AIAAwbpw Date: Wed, 5 Feb 2025 10:43:53 +0000 Message-ID: References: <20241108125242.60136-1-shameerali.kolothum.thodi@huawei.com> <329445b2f68a47269292aefb34584375@huawei.com> <77f736f6-9ef9-462b-916e-c8cfff279044@redhat.com> In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.203.177.241] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Received-SPF: pass client-ip=185.176.79.56; envelope-from=shameerali.kolothum.thodi@huawei.com; helo=frasgout.his.huawei.com X-Spam_score_int: -4 X-Spam_score: -0.5 X-Spam_bar: / X-Spam_report: (-0.5 / 5.0 requ) BAYES_00=-1.9, PDS_BTC_ID=0.499, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, THREAD_INDEX_BAD=3.199 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-to: Shameerali Kolothum Thodi From: Shameerali Kolothum Thodi via Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org > -----Original Message----- > From: Nicolin Chen > Sent: Wednesday, February 5, 2025 12:09 AM > To: Shameerali Kolothum Thodi > ; Eric Auger > > Cc: ddutile@redhat.com; Peter Maydell ; Jason > Gunthorpe ; Daniel P. Berrang=E9 ; > qemu-arm@nongnu.org; qemu-devel@nongnu.org; Linuxarm > ; Wangzhou (B) ; > jiangkunkun ; Jonathan Cameron > ; zhangfei.gao@linaro.org > Subject: Re: [RFC PATCH 0/5] hw/arm/virt: Add support for user-creatable > nested SMMUv3 >=20 > On Tue, Feb 04, 2025 at 06:49:15PM +0100, Eric Auger wrote: > > > In summary, we will have the following series: > > > 1) HWPT uAPI patches in backends/iommufd.c (Zhenzhong or Shameer) > > > https://lore.kernel.org/qemu- > devel/SJ0PR11MB6744943702EB5798EC9B3B9992E02@SJ0PR11MB6744.nam > prd11.prod.outlook.com/ > > > 2) vIOMMU uAPI patches in backends/iommufd.c (I will rebase/send) >=20 > > for 1 and 2, are you taking about the "Add VIOMMU infrastructure > support > > " series in Shameer's branch: private-smmuv3-nested-dev-rfc-v1. > > Sorry I may instead refer to NVidia or Intel's branch but I am not sure > > about the last ones. >=20 > That "vIOMMU infrastructure" is for 2, yes. >=20 > For 1, it's inside the Intel's series: > "cover-letter: intel_iommu: Enable stage-1 translation for passthrough > device" >=20 > So, we need to extract them out and make it separately.. >=20 > > > 3) vSMMUv3 patches for HW-acc/nesting (Hoping Don/you could take > over) > > We can start sending it upstream assuming we have a decent test > environment. > > > > However in > > > https://lore.kernel.org/all/329445b2f68a47269292aefb34584375@huawei.c > om/ > > > > Shameer suggested he may include it in his SMMU multi instance series. > > What do you both prefer? >=20 > Sure, I think it's good to include those patches, though I believe > we need to build a new shared branch as Shameer's branch might not > reflect the latest kernel uAPI header. >=20 > Here is a new branch on top of latest master tree (v9.2.50): > https://github.com/nicolinc/qemu/commits/wip/for_shameer_02042025 >=20 > I took HWPT patches from Zhenzhong's series and rebased all related > changes from my tree. I did some sanity and it should work with RMR. >=20 > Shameer, would you please try this branch and then integrate your > series on top of the following series? > cover-letter: Add HW accelerated nesting support for arm SMMUv3 > cover-letter: Add vIOMMU-based nesting infrastructure support > cover-letter: Add HWPT-based nesting infrastructure support > Basically, just replace my old multi-instance series with yours, to > create a shared branch for all of us. Ok. I will take a look at that and rebase. Thanks, Shameer