LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Robin Murphy <robin.murphy@arm.com> To: joro@8bytes.org, will@kernel.org Cc: iommu@lists.linux-foundation.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, suravee.suthikulpanit@amd.com, baolu.lu@linux.intel.com, john.garry@huawei.com, dianders@chromium.org, rajatja@google.com, chenxiang66@hisilicon.com, Sai Praneeth Prakhya <sai.praneeth.prakhya@intel.com> Subject: [PATCH v3 21/25] iommu: Expose DMA domain strictness via sysfs Date: Wed, 4 Aug 2021 18:15:49 +0100 [thread overview] Message-ID: <fca07df20f45952ff5c19b744fc87be777259594.1628094601.git.robin.murphy@arm.com> (raw) In-Reply-To: <cover.1628094600.git.robin.murphy@arm.com> The sysfs interface for default domain types exists primarily so users can choose the performance/security tradeoff relevant to their own workload. As such, the choice between the policies for DMA domains fits perfectly as an additional point on that scale - downgrading a particular device from a strict default to non-strict may be enough to let it reach the desired level of performance, while still retaining more peace of mind than with a wide-open identity domain. Now that we've abstracted non-strict mode as a distinct type of DMA domain, allow it to be chosen through the user interface as well. CC: Sai Praneeth Prakhya <sai.praneeth.prakhya@intel.com> Reviewed-by: Lu Baolu <baolu.lu@linux.intel.com> Reviewed-by: John Garry <john.garry@huawei.com> Signed-off-by: Robin Murphy <robin.murphy@arm.com> --- v3: Summarise the implications in the documentation for completeness --- Documentation/ABI/testing/sysfs-kernel-iommu_groups | 6 +++++- drivers/iommu/iommu.c | 2 ++ 2 files changed, 7 insertions(+), 1 deletion(-) diff --git a/Documentation/ABI/testing/sysfs-kernel-iommu_groups b/Documentation/ABI/testing/sysfs-kernel-iommu_groups index eae2f1c1e11e..b15af6a5bc08 100644 --- a/Documentation/ABI/testing/sysfs-kernel-iommu_groups +++ b/Documentation/ABI/testing/sysfs-kernel-iommu_groups @@ -42,8 +42,12 @@ Description: /sys/kernel/iommu_groups/<grp_id>/type shows the type of default ======== ====================================================== DMA All the DMA transactions from the device in this group are translated by the iommu. + DMA-FQ As above, but using batched invalidation to lazily + remove translations after use. This may offer reduced + overhead at the cost of reduced memory protection. identity All the DMA transactions from the device in this group - are not translated by the iommu. + are not translated by the iommu. Maximum performance + but zero protection. auto Change to the type the device was booted with. ======== ====================================================== diff --git a/drivers/iommu/iommu.c b/drivers/iommu/iommu.c index 55ca5bf3cafc..b141161d5bbc 100644 --- a/drivers/iommu/iommu.c +++ b/drivers/iommu/iommu.c @@ -3267,6 +3267,8 @@ static ssize_t iommu_group_store_type(struct iommu_group *group, req_type = IOMMU_DOMAIN_IDENTITY; else if (sysfs_streq(buf, "DMA")) req_type = IOMMU_DOMAIN_DMA; + else if (sysfs_streq(buf, "DMA-FQ")) + req_type = IOMMU_DOMAIN_DMA_FQ; else if (sysfs_streq(buf, "auto")) req_type = 0; else -- 2.25.1
next prev parent reply other threads:[~2021-08-04 17:17 UTC|newest] Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-04 17:15 [PATCH v3 00/25] iommu: Refactor DMA domain strictness Robin Murphy 2021-08-04 17:15 ` [PATCH v3 01/25] iommu: Pull IOVA cookie management into the core Robin Murphy 2021-08-04 18:52 ` Heiko Stübner 2021-08-05 7:18 ` Marek Szyprowski 2021-08-05 9:15 ` Yoshihiro Shimoda 2021-08-04 17:15 ` [PATCH v3 02/25] iommu/amd: Drop IOVA cookie management Robin Murphy 2021-08-05 7:37 ` kernel test robot 2021-08-05 9:37 ` Robin Murphy 2021-08-04 17:15 ` [PATCH v3 03/25] iommu/arm-smmu: " Robin Murphy 2021-08-04 17:15 ` [PATCH v3 04/25] iommu/vt-d: " Robin Murphy 2021-08-04 17:15 ` [PATCH v3 05/25] iommu/exynos: " Robin Murphy 2021-08-05 7:19 ` Marek Szyprowski 2021-08-04 17:15 ` [PATCH v3 06/25] iommu/ipmmu-vmsa: " Robin Murphy 2021-08-05 9:15 ` Yoshihiro Shimoda 2021-08-04 17:15 ` [PATCH v3 07/25] iommu/mtk: " Robin Murphy 2021-08-04 17:15 ` [PATCH v3 08/25] iommu/rockchip: " Robin Murphy 2021-08-04 18:53 ` Heiko Stübner 2021-08-04 17:15 ` [PATCH v3 09/25] iommu/sprd: " Robin Murphy 2021-08-06 2:15 ` Chunyan Zhang 2021-08-04 17:15 ` [PATCH v3 10/25] iommu/sun50i: " Robin Murphy 2021-08-04 17:15 ` [PATCH v3 11/25] iommu/virtio: " Robin Murphy 2021-08-04 17:15 ` [PATCH v3 12/25] iommu/dma: Unexport " Robin Murphy 2021-08-04 17:15 ` [PATCH v3 13/25] iommu/dma: Remove redundant "!dev" checks Robin Murphy 2021-08-04 17:15 ` [PATCH v3 14/25] iommu: Indicate queued flushes via gather data Robin Murphy 2021-08-04 17:15 ` [PATCH v3 15/25] iommu/io-pgtable: Remove non-strict quirk Robin Murphy 2021-08-04 17:15 ` [PATCH v3 16/25] iommu: Introduce explicit type for non-strict DMA domains Robin Murphy 2021-08-04 17:15 ` [PATCH v3 17/25] iommu/amd: Prepare for multiple DMA domain types Robin Murphy 2021-08-04 17:15 ` [PATCH v3 18/25] iommu/arm-smmu: " Robin Murphy 2021-08-04 17:15 ` [PATCH v3 19/25] iommu/vt-d: " Robin Murphy 2021-08-04 17:15 ` [PATCH v3 20/25] iommu: Express DMA strictness via the domain type Robin Murphy 2021-08-04 17:15 ` Robin Murphy [this message] 2021-08-04 17:15 ` [PATCH v3 22/25] iommu: Only log strictness for DMA domains Robin Murphy 2021-08-04 17:15 ` [PATCH v3 23/25] iommu: Merge strictness and domain type configs Robin Murphy 2021-08-06 9:15 ` John Garry 2021-08-04 17:15 ` [PATCH v3 24/25] iommu/dma: Factor out flush queue init Robin Murphy 2021-08-09 12:52 ` Will Deacon 2021-08-09 14:47 ` Robin Murphy 2021-08-09 19:05 ` Rajat Jain 2021-08-09 19:59 ` Robin Murphy 2021-08-09 20:15 ` Rajat Jain 2021-08-04 17:15 ` [PATCH v3 25/25] iommu: Allow enabling non-strict mode dynamically Robin Murphy 2021-08-09 12:49 ` Will Deacon 2021-08-09 13:40 ` Robin Murphy
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=fca07df20f45952ff5c19b744fc87be777259594.1628094601.git.robin.murphy@arm.com \ --to=robin.murphy@arm.com \ --cc=baolu.lu@linux.intel.com \ --cc=chenxiang66@hisilicon.com \ --cc=dianders@chromium.org \ --cc=iommu@lists.linux-foundation.org \ --cc=john.garry@huawei.com \ --cc=joro@8bytes.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=rajatja@google.com \ --cc=sai.praneeth.prakhya@intel.com \ --cc=suravee.suthikulpanit@amd.com \ --cc=will@kernel.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).