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 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 smtp.lore.kernel.org (Postfix) with ESMTPS id A0DC3C4828F for ; Fri, 9 Feb 2024 13:54:36 +0000 (UTC) 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:MIME-Version:In-Reply-To:References: Message-ID:Date:Subject:CC:To:From:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=oti3qvHIuPFdeEo5i+bxdFGoUEYmwJqA4N1JILTN5fE=; b=G6MQ2ktG4I+yUf 6Atfmu/yhWftwEL2Vf+jc9F6XUME5RFoVV8ygTkjLoxKn2yPjxeHmGny5zjQc6ns1Jx/zDDqzs2bq V0o6k3M9gFWRvKz7uYb1og7weiJwHYAFM4uyi1IOpZe58JVSafD+eGmGd9y4pmc3LuGYbhnlX9vcQ 9ehNuXk5KaqEACS6SaMgVDBfhWHQGKCYs97Fq7jal3RNma2RfTkc4HGfG4+fJG/cqRD9n+xyA2DMy dpWCMqKguwP+wPt3ln98cEDcwfX02UPyAQNh8osyzADp2OusV4XGlpzF0KHdWyqOi81a4sFNPTtCZ Rg5M0efVFcnB7bFmytpg==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.97.1 #2 (Red Hat Linux)) id 1rYRKi-0000000H7YR-2Y31; Fri, 09 Feb 2024 13:54:24 +0000 Received: from frasgout.his.huawei.com ([185.176.79.56]) by bombadil.infradead.org with esmtps (Exim 4.97.1 #2 (Red Hat Linux)) id 1rYRKf-0000000H7WN-0Fd4 for linux-arm-kernel@lists.infradead.org; Fri, 09 Feb 2024 13:54:22 +0000 Received: from mail.maildlp.com (unknown [172.18.186.31]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4TWZxC2CFCz6JB14; Fri, 9 Feb 2024 21:50:23 +0800 (CST) Received: from lhrpeml500002.china.huawei.com (unknown [7.191.160.78]) by mail.maildlp.com (Postfix) with ESMTPS id C046E140595; Fri, 9 Feb 2024 21:54:08 +0800 (CST) Received: from lhrpeml500005.china.huawei.com (7.191.163.240) by lhrpeml500002.china.huawei.com (7.191.160.78) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.35; Fri, 9 Feb 2024 13:54:08 +0000 Received: from lhrpeml500005.china.huawei.com ([7.191.163.240]) by lhrpeml500005.china.huawei.com ([7.191.163.240]) with mapi id 15.01.2507.035; Fri, 9 Feb 2024 13:54:08 +0000 From: Shameerali Kolothum Thodi To: Jean-Philippe Brucker CC: "kvmarm@lists.linux.dev" , "iommu@lists.linux.dev" , "linux-arm-kernel@lists.infradead.org" , Linuxarm , "kevin.tian@intel.com" , "jgg@ziepe.ca" , "alex.williamson@redhat.com" , "maz@kernel.org" , "oliver.upton@linux.dev" , "will@kernel.org" , "robin.murphy@arm.com" , Jonathan Cameron Subject: RE: [RFC PATCH v2 0/7] iommu/arm-smmu-v3: Use pinned KVM VMID for stage 2 Thread-Topic: [RFC PATCH v2 0/7] iommu/arm-smmu-v3: Use pinned KVM VMID for stage 2 Thread-Index: AQHaWqKd0D2tjroZbEixT8fjcriLLrEB6UwAgAAfllA= Date: Fri, 9 Feb 2024 13:54:08 +0000 Message-ID: <1f0e938bbf684fe69ad7050b8cb3cc29@huawei.com> References: <20240208151837.35068-1-shameerali.kolothum.thodi@huawei.com> <20240209115824.GA2922446@myrica> In-Reply-To: <20240209115824.GA2922446@myrica> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.202.227.28] MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240209_055421_287623_58BEB1F4 X-CRM114-Status: GOOD ( 15.59 ) 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 > -----Original Message----- > From: Jean-Philippe Brucker > Sent: Friday, February 9, 2024 11:58 AM > To: Shameerali Kolothum Thodi > Cc: kvmarm@lists.linux.dev; iommu@lists.linux.dev; linux-arm- > kernel@lists.infradead.org; Linuxarm ; > kevin.tian@intel.com; jgg@ziepe.ca; alex.williamson@redhat.com; > maz@kernel.org; oliver.upton@linux.dev; will@kernel.org; > robin.murphy@arm.com; Jonathan Cameron > > Subject: Re: [RFC PATCH v2 0/7] iommu/arm-smmu-v3: Use pinned KVM > VMID for stage 2 > > Hi Shameer, > > On Thu, Feb 08, 2024 at 03:18:30PM +0000, Shameer Kolothum wrote: > > Hi, > > > > On an ARM64 system with a SMMUv3 implementation that fully supports > > Broadcast TLB Maintenance(BTM) feature as part of the Distributed > > Virtual Memory(DVM) protocol, the CPU TLB invalidate instructions are > > received by SMMUv3. This is very useful when the SMMUv3 shares the > > page tables with the CPU(eg: Guest SVA use case). For this to work, > > the SMMUv3 must use the same VMID that is allocated by KVM to > configure > > the nested stage 2(S2) translations. > > The series makes sense to me. Maybe a little more detail to help the KVM > maintainers understand why we need something like this even though the s2 > page tables aren't shared between CPU and SMMU: Thanks Jean for the nice write up. I will use this for next revisions of this series. Shameer _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel