Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp2876136pxj; Mon, 14 Jun 2021 09:07:16 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwjYwKLYINjM+VIOaj8+QIL6zx0va8scVYZA+d70lEMB8NTKdcy8x4U6UYYA6U9hCVuF/eR X-Received: by 2002:a50:b2c5:: with SMTP id p63mr4203378edd.5.1623686836317; Mon, 14 Jun 2021 09:07:16 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1623686836; cv=none; d=google.com; s=arc-20160816; b=HR5SVfgGNJnKS4G62zv9+fS3S1xdJznxxcTdDSLZrO6Inj0CB5TYSKaiqvZgs/1Eiz 2qfWRALQlkFv1yGiA6mypVz04lCIqhdzwrg96KlTfYiclmIByEq3y6CjKOUqNc4r3miU mkRJgaMNluZd2dcdLpBTVGX4mxeAUu3bZqcOZlndau+T7nDiqqJAV1lAujIU65ktWRLZ lWSsS/V/6phzm8e9huEf/ZGRyQiIeP/rkmcVqEvlBGj80hWgWRSl10xNLD2+Xe7Xybsl zAA+tsuFcP+kC8z6PfBgFgsi+FlcukxTOw0VqyNOK15n6soZ26UtcI8F0OQ3EUza+xxH J66w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=lLw/IypvhBG6vMh7QkkW1BS/LupX5MpetLPOw3qTuo4=; b=khOcL9iaR9qVBuH+2bNv8vLT+owu/u2rI3ZnwEVC7ec16Q6JWHuZciSY1+dv3J3bbS P0J4SD7X1Jn6hRuWT58ILJsQP6jq4JOK5C2k/2swnf39c4xqv630EUgUrNlvcRq2JtHs neXVC19hIY77IgMiOANbbV3iEVtn7qOSgCpzHCyScswekP8Li6o0cyZ9gtJXhd627UmA 3nM2xoYdCjBvH8BajQEs3JQrvZ+jstdglAHLoVBbHGLdfjOC5lV6s/6bj9MZJxq8PkEk UlwWyX0KBt3OrvNd5KTx6uoSgfSaKi2iVWnTYsmO136ajfQ35d4GQBz0gS6uamtPvBUl 1qAA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id a25si11907980edt.496.2021.06.14.09.06.53; Mon, 14 Jun 2021 09:07:16 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234211AbhFNQFo (ORCPT + 99 others); Mon, 14 Jun 2021 12:05:44 -0400 Received: from foss.arm.com ([217.140.110.172]:39860 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233135AbhFNQFl (ORCPT ); Mon, 14 Jun 2021 12:05:41 -0400 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 932A21FB; Mon, 14 Jun 2021 09:03:38 -0700 (PDT) Received: from [10.57.9.136] (unknown [10.57.9.136]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id D39653F70D; Mon, 14 Jun 2021 09:03:36 -0700 (PDT) Subject: Re: [PATCH v12 2/5] iommu: Enhance IOMMU default DMA mode build options To: John Garry , joro@8bytes.org, will@kernel.org, dwmw2@infradead.org, baolu.lu@linux.intel.com Cc: linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org, linuxarm@huawei.com, thunder.leizhen@huawei.com, chenxiang66@hisilicon.com References: <1623414043-40745-1-git-send-email-john.garry@huawei.com> <1623414043-40745-3-git-send-email-john.garry@huawei.com> From: Robin Murphy Message-ID: <2fe7d268-bc9f-9808-29a5-610527a0fd32@arm.com> Date: Mon, 14 Jun 2021 17:03:31 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; rv:78.0) Gecko/20100101 Thunderbird/78.10.1 MIME-Version: 1.0 In-Reply-To: <1623414043-40745-3-git-send-email-john.garry@huawei.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2021-06-11 13:20, John Garry wrote: > From: Zhen Lei > > First, add build options IOMMU_DEFAULT_{LAZY|STRICT}, so that we have the > opportunity to set {lazy|strict} mode as default at build time. Then put > the two config options in an choice, as they are mutually exclusive. > > [jpg: Make choice between strict and lazy only (and not passthrough)] > Signed-off-by: Zhen Lei > Signed-off-by: John Garry > --- > drivers/iommu/Kconfig | 38 ++++++++++++++++++++++++++++++++++++++ > drivers/iommu/iommu.c | 3 ++- > 2 files changed, 40 insertions(+), 1 deletion(-) > > diff --git a/drivers/iommu/Kconfig b/drivers/iommu/Kconfig > index 1f111b399bca..2a71347611d4 100644 > --- a/drivers/iommu/Kconfig > +++ b/drivers/iommu/Kconfig > @@ -90,6 +90,44 @@ config IOMMU_DEFAULT_PASSTHROUGH > > If unsure, say N here. > > +choice > + prompt "IOMMU default DMA mode" > + depends on IOMMU_DMA > + > + default IOMMU_DEFAULT_STRICT > + help > + This option allows an IOMMU DMA mode to be chosen at build time, to > + override the default DMA mode of each ARCH, removing the need to > + pass in kernel parameters through command line. It is still possible > + to provide ARCH-specific or common boot options to override this > + option. > + > + If unsure, keep the default. > + > +config IOMMU_DEFAULT_STRICT > + bool "strict" > + help > + For every IOMMU DMA unmap operation, the flush operation of IOTLB and > + the free operation of IOVA are guaranteed to be done in the unmap > + function. > + > +config IOMMU_DEFAULT_LAZY > + bool "lazy" > + help > + Support lazy mode, where for every IOMMU DMA unmap operation, the > + flush operation of IOTLB and the free operation of IOVA are deferred. > + They are only guaranteed to be done before the related IOVA will be > + reused. > + > + The isolation provided in this mode is not as secure as STRICT mode, > + such that a vulnerable time window may be created between the DMA > + unmap and the mapping finally being torn down in the IOMMU, where the > + device can still access the system memory. However this mode may > + provide better performance in high throughput scenarios, and is still > + considerably more secure than passthrough mode or no IOMMU. > + > +endchoice > + > config OF_IOMMU > def_bool y > depends on OF && IOMMU_API > diff --git a/drivers/iommu/iommu.c b/drivers/iommu/iommu.c > index cf58949cc2f3..ccbd5d4c1a50 100644 > --- a/drivers/iommu/iommu.c > +++ b/drivers/iommu/iommu.c > @@ -29,7 +29,8 @@ static struct kset *iommu_group_kset; > static DEFINE_IDA(iommu_group_ida); > > static unsigned int iommu_def_domain_type __read_mostly; > -static bool iommu_dma_strict __read_mostly = true; > +static bool iommu_dma_strict __read_mostly = > + IS_ENABLED(CONFIG_IOMMU_DEFAULT_STRICT); Nit: I reckon this is a fine place to wield the 100-character relaxation, but it's not my call in the end. With the wording tweaks already mentioned, Reviewed-by: Robin Murphy > static u32 iommu_cmd_line __read_mostly; > > struct iommu_group { >