Received: by 2002:a05:6a10:1287:0:0:0:0 with SMTP id d7csp6691344pxv; Thu, 29 Jul 2021 23:14:21 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzVEKTLegM2Fh7BPToXsBhBPfz4hVgpdDURvn5K4LQk6tSOSNXlrCXKHPeVkqZrMiPi6sPX X-Received: by 2002:a5d:93d3:: with SMTP id j19mr1106554ioo.184.1627625661572; Thu, 29 Jul 2021 23:14:21 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1627625661; cv=none; d=google.com; s=arc-20160816; b=J720vX/zAntvCT1LXN4p0+n0rGABnnlMY6M1RFyIo/PrqzBuojkc+qZ0aHRN3cLTfz jow5PeaR8uQiNnuRkJ0QJ7YZa/yTLrjEF7fqLLXYvSo1dSJxf5sMezYX2TGy/5lM51hm yacArJD5OaJ3l+5L2lKp+OI/lFHlvYZbXFUWKUcwHjtikqndknMkUS+GBdRNbM3fgclF uuA9VXNeh31dAr4tPTmPAhfUohuQu/MkjQDX1S9fzhINrBv3oui9ujseCWR01my1r7QP 5L7tYzaToUHyNS0EdfPBryjMPxwqu2/lLhgbJbb1Q30MiT7nD7X4/8jHQKAxIIy23aWY eXzg== 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 :to:subject:cc; bh=i3YVU+zVvrwfBsvQvRYjFD9xK3buBmBKsSNHXJ7R6wQ=; b=XYQU4kwGZ8thAlvxq95e7299nOcE6qXeA1jtayAplXJJULDcBAQfeW4yADWPdWLVtw IW4pLs9nwBaIt+3C/O/vO7Ez/8/tsyuPklcqPfgwZfkRab8A0n9l66fXpKMbhQmZ45AR T0og+Hse3y2LBxlyRr0Vxyux9ZSq8UKSDfyhv4SXjb/nwwpvOTV6DESKa83N3hX6WtO6 ThzS/CvM0LfQSmzKE/kwFzcVSdvoQUXA+Sl3b6qEASvoJWVBGCGtNnfvPEpPR7LxxXrN L0agw+tGhRRsEdnKHqFRQCCjIyTIxJSya8nHXTujj9+iJ1KRh0CvN11rZugC1TgfGnCr oVKg== 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=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id w21si653154jah.86.2021.07.29.23.14.09; Thu, 29 Jul 2021 23:14:21 -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=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237349AbhG3GNO (ORCPT + 99 others); Fri, 30 Jul 2021 02:13:14 -0400 Received: from mga11.intel.com ([192.55.52.93]:42060 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237060AbhG3GNN (ORCPT ); Fri, 30 Jul 2021 02:13:13 -0400 X-IronPort-AV: E=McAfee;i="6200,9189,10060"; a="209926199" X-IronPort-AV: E=Sophos;i="5.84,281,1620716400"; d="scan'208";a="209926199" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 29 Jul 2021 23:13:09 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.84,281,1620716400"; d="scan'208";a="465345218" Received: from allen-box.sh.intel.com (HELO [10.239.159.118]) ([10.239.159.118]) by orsmga008.jf.intel.com with ESMTP; 29 Jul 2021 23:13:06 -0700 Cc: baolu.lu@linux.intel.com, iommu@lists.linux-foundation.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, suravee.suthikulpanit@amd.com, john.garry@huawei.com, dianders@chromium.org Subject: Re: [PATCH v2 20/24] iommu: Merge strictness and domain type configs To: Robin Murphy , joro@8bytes.org, will@kernel.org References: <992b2952f0b173411c7b6f221dce82e8e082c0b8.1627468310.git.robin.murphy@arm.com> From: Lu Baolu Message-ID: <2c714d77-1852-fe0f-7dcf-aabe09726619@linux.intel.com> Date: Fri, 30 Jul 2021 14:10:48 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 MIME-Version: 1.0 In-Reply-To: <992b2952f0b173411c7b6f221dce82e8e082c0b8.1627468310.git.robin.murphy@arm.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 7/28/21 11:58 PM, Robin Murphy wrote: > To parallel the sysfs behaviour, merge the new build-time option > for DMA domain strictness into the default domain type choice. > > Suggested-by: Joerg Roedel > Signed-off-by: Robin Murphy > --- > drivers/iommu/Kconfig | 80 +++++++++++++++++++++---------------------- > drivers/iommu/iommu.c | 2 +- > 2 files changed, 41 insertions(+), 41 deletions(-) > > diff --git a/drivers/iommu/Kconfig b/drivers/iommu/Kconfig > index c84da8205be7..6e06f876d75a 100644 > --- a/drivers/iommu/Kconfig > +++ b/drivers/iommu/Kconfig > @@ -79,55 +79,55 @@ config IOMMU_DEBUGFS > debug/iommu directory, and then populate a subdirectory with > entries as required. > > -config IOMMU_DEFAULT_PASSTHROUGH > - bool "IOMMU passthrough by default" > - depends on IOMMU_API > - help > - Enable passthrough by default, removing the need to pass in > - iommu.passthrough=on or iommu=pt through command line. If this > - is enabled, you can still disable with iommu.passthrough=off > - or iommu=nopt depending on the architecture. > - > - If unsure, say N here. > - > choice > - prompt "IOMMU default DMA IOTLB invalidation mode" > - depends on IOMMU_DMA > - > - default IOMMU_DEFAULT_LAZY if (AMD_IOMMU || INTEL_IOMMU) > - default IOMMU_DEFAULT_STRICT > + prompt "IOMMU default domain type" > + depends on IOMMU_API > + default IOMMU_DEFAULT_DMA_LAZY if AMD_IOMMU || INTEL_IOMMU > + default IOMMU_DEFAULT_DMA_STRICT > help > - This option allows an IOMMU DMA IOTLB invalidation mode to be > - chosen at build time, to override the default mode of each ARCH, > - removing the need to pass in kernel parameters through command line. > - It is still possible to provide common boot params to override this > - config. > + Choose the type of IOMMU domain used to manage DMA API usage by > + device drivers. The options here typically represent different > + levels of tradeoff between robustness/security and performance, > + depending on the IOMMU driver. Not all IOMMUs support all options. > + This choice can be overridden at boot via the command line, and for > + some devices also at runtime via sysfs. > > If unsure, keep the default. > > -config IOMMU_DEFAULT_STRICT > - bool "strict" > +config IOMMU_DEFAULT_DMA_STRICT > + bool "Translated - 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. > + Trusted devices use translation to restrict their access to only > + DMA-mapped pages, with strict TLB invalidation on unmap. Equivalent > + to passing "iommu.passthrough=0 iommu.strict=1" on the command line. > > -config IOMMU_DEFAULT_LAZY > - bool "lazy" > + Untrusted devices always use this mode, with an additional layer of > + bounce-buffering such that they cannot gain access to any unrelated > + data within a mapped page. > + > +config IOMMU_DEFAULT_DMA_LAZY > + bool "Translated - 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. > + Trusted devices use translation to restrict their access to only > + DMA-mapped pages, but with "lazy" batched TLB invalidation. This > + mode allows higher performance with some IOMMUs due to reduced TLB > + flushing, but at the cost of reduced isolation since devices may be > + able to access memory for some time after it has been unmapped. > + Equivalent to passing "iommu.passthrough=0 iommu.strict=0" on the > + command line. > > - 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 mappings cached in the IOMMU IOTLB or device TLB > - finally being invalidated, where the device could still access the > - memory which has already been unmapped by the device driver. > - However this mode may provide better performance in high throughput > - scenarios, and is still considerably more secure than passthrough > - mode or no IOMMU. > + If this mode is not supported by the IOMMU driver, the effective > + runtime default will fall back to IOMMU_DEFAULT_DMA_STRICT. > + > +config IOMMU_DEFAULT_PASSTHROUGH > + bool "Passthrough" > + help > + Trusted devices are identity-mapped, giving them unrestricted access > + to memory with minimal performance overhead. Equivalent to passing > + "iommu.passthrough=1" (historically "iommu=pt") on the command line. > + > + If this mode is not supported by the IOMMU driver, the effective > + runtime default will fall back to IOMMU_DEFAULT_DMA_STRICT. > > endchoice > > diff --git a/drivers/iommu/iommu.c b/drivers/iommu/iommu.c > index 5a08e0806cbb..25c1adc1ec67 100644 > --- a/drivers/iommu/iommu.c > +++ b/drivers/iommu/iommu.c > @@ -31,7 +31,7 @@ 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 = IS_ENABLED(CONFIG_IOMMU_DEFAULT_STRICT); > +static bool iommu_dma_strict __read_mostly = IS_ENABLED(CONFIG_IOMMU_DEFAULT_DMA_STRICT); > static u32 iommu_cmd_line __read_mostly; > > struct iommu_group { > Reviewed-by: Lu Baolu Best regards, baolu