All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean-Philippe Brucker <jean-philippe@linaro.org>
To: Robin Murphy <robin.murphy@arm.com>
Cc: joro@8bytes.org, will@kernel.org, linux-kernel@vger.kernel.org,
	dianders@chromium.org, iommu@lists.linux-foundation.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 19/24] iommu: Expose DMA domain strictness via sysfs
Date: Fri, 30 Jul 2021 11:28:23 +0200	[thread overview]
Message-ID: <YQPGNxhgVEagZ28H@myrica> (raw)
In-Reply-To: <dd26592103c7613ef9fdff703d0d2ed2df8305c2.1627468310.git.robin.murphy@arm.com>

On Wed, Jul 28, 2021 at 04:58:40PM +0100, Robin Murphy wrote:
> 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.
> 
> Signed-off-by: Robin Murphy <robin.murphy@arm.com>
> ---
>  Documentation/ABI/testing/sysfs-kernel-iommu_groups | 2 ++
>  drivers/iommu/iommu.c                               | 2 ++
>  2 files changed, 4 insertions(+)
> 
> diff --git a/Documentation/ABI/testing/sysfs-kernel-iommu_groups b/Documentation/ABI/testing/sysfs-kernel-iommu_groups
> index eae2f1c1e11e..43ba764ba5b7 100644
> --- a/Documentation/ABI/testing/sysfs-kernel-iommu_groups
> +++ b/Documentation/ABI/testing/sysfs-kernel-iommu_groups
> @@ -42,6 +42,8 @@ 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.

It might be useful to desribe the security/performance tradeoff here as
well. I guess a normal user is more likely to look at the doc for this
sysfs knob than the kernel config or parameters.

Thanks,
Jean

>  		identity  All the DMA transactions from the device in this group
>  		          are not translated by the iommu.
>  		auto      Change to the type the device was booted with.
> diff --git a/drivers/iommu/iommu.c b/drivers/iommu/iommu.c
> index eecb5657de69..5a08e0806cbb 100644
> --- a/drivers/iommu/iommu.c
> +++ b/drivers/iommu/iommu.c
> @@ -3265,6 +3265,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
> 
> _______________________________________________
> iommu mailing list
> iommu@lists.linux-foundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/iommu

WARNING: multiple messages have this Message-ID (diff)
From: Jean-Philippe Brucker <jean-philippe@linaro.org>
To: Robin Murphy <robin.murphy@arm.com>
Cc: linux-kernel@vger.kernel.org, dianders@chromium.org,
	iommu@lists.linux-foundation.org, will@kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 19/24] iommu: Expose DMA domain strictness via sysfs
Date: Fri, 30 Jul 2021 11:28:23 +0200	[thread overview]
Message-ID: <YQPGNxhgVEagZ28H@myrica> (raw)
In-Reply-To: <dd26592103c7613ef9fdff703d0d2ed2df8305c2.1627468310.git.robin.murphy@arm.com>

On Wed, Jul 28, 2021 at 04:58:40PM +0100, Robin Murphy wrote:
> 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.
> 
> Signed-off-by: Robin Murphy <robin.murphy@arm.com>
> ---
>  Documentation/ABI/testing/sysfs-kernel-iommu_groups | 2 ++
>  drivers/iommu/iommu.c                               | 2 ++
>  2 files changed, 4 insertions(+)
> 
> diff --git a/Documentation/ABI/testing/sysfs-kernel-iommu_groups b/Documentation/ABI/testing/sysfs-kernel-iommu_groups
> index eae2f1c1e11e..43ba764ba5b7 100644
> --- a/Documentation/ABI/testing/sysfs-kernel-iommu_groups
> +++ b/Documentation/ABI/testing/sysfs-kernel-iommu_groups
> @@ -42,6 +42,8 @@ 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.

It might be useful to desribe the security/performance tradeoff here as
well. I guess a normal user is more likely to look at the doc for this
sysfs knob than the kernel config or parameters.

Thanks,
Jean

>  		identity  All the DMA transactions from the device in this group
>  		          are not translated by the iommu.
>  		auto      Change to the type the device was booted with.
> diff --git a/drivers/iommu/iommu.c b/drivers/iommu/iommu.c
> index eecb5657de69..5a08e0806cbb 100644
> --- a/drivers/iommu/iommu.c
> +++ b/drivers/iommu/iommu.c
> @@ -3265,6 +3265,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
> 
> _______________________________________________
> iommu mailing list
> iommu@lists.linux-foundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/iommu
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

WARNING: multiple messages have this Message-ID (diff)
From: Jean-Philippe Brucker <jean-philippe@linaro.org>
To: Robin Murphy <robin.murphy@arm.com>
Cc: joro@8bytes.org, will@kernel.org, linux-kernel@vger.kernel.org,
	dianders@chromium.org, iommu@lists.linux-foundation.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 19/24] iommu: Expose DMA domain strictness via sysfs
Date: Fri, 30 Jul 2021 11:28:23 +0200	[thread overview]
Message-ID: <YQPGNxhgVEagZ28H@myrica> (raw)
In-Reply-To: <dd26592103c7613ef9fdff703d0d2ed2df8305c2.1627468310.git.robin.murphy@arm.com>

On Wed, Jul 28, 2021 at 04:58:40PM +0100, Robin Murphy wrote:
> 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.
> 
> Signed-off-by: Robin Murphy <robin.murphy@arm.com>
> ---
>  Documentation/ABI/testing/sysfs-kernel-iommu_groups | 2 ++
>  drivers/iommu/iommu.c                               | 2 ++
>  2 files changed, 4 insertions(+)
> 
> diff --git a/Documentation/ABI/testing/sysfs-kernel-iommu_groups b/Documentation/ABI/testing/sysfs-kernel-iommu_groups
> index eae2f1c1e11e..43ba764ba5b7 100644
> --- a/Documentation/ABI/testing/sysfs-kernel-iommu_groups
> +++ b/Documentation/ABI/testing/sysfs-kernel-iommu_groups
> @@ -42,6 +42,8 @@ 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.

It might be useful to desribe the security/performance tradeoff here as
well. I guess a normal user is more likely to look at the doc for this
sysfs knob than the kernel config or parameters.

Thanks,
Jean

>  		identity  All the DMA transactions from the device in this group
>  		          are not translated by the iommu.
>  		auto      Change to the type the device was booted with.
> diff --git a/drivers/iommu/iommu.c b/drivers/iommu/iommu.c
> index eecb5657de69..5a08e0806cbb 100644
> --- a/drivers/iommu/iommu.c
> +++ b/drivers/iommu/iommu.c
> @@ -3265,6 +3265,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
> 
> _______________________________________________
> iommu mailing list
> iommu@lists.linux-foundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/iommu

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2021-07-30  9:28 UTC|newest]

Thread overview: 195+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-28 15:58 [PATCH v2 00/24] iommu: Refactor DMA domain strictness Robin Murphy
2021-07-28 15:58 ` Robin Murphy
2021-07-28 15:58 ` Robin Murphy
2021-07-28 15:58 ` [PATCH v2 01/24] iommu: Pull IOVA cookie management into the core Robin Murphy
2021-07-28 15:58   ` Robin Murphy
2021-07-28 15:58   ` Robin Murphy
2021-07-30  6:06   ` Lu Baolu
2021-07-30  6:06     ` Lu Baolu
2021-07-30  6:06     ` Lu Baolu
2021-07-30  9:32   ` Jean-Philippe Brucker
2021-07-30  9:32     ` Jean-Philippe Brucker
2021-07-30  9:32     ` Jean-Philippe Brucker
2021-07-28 15:58 ` [PATCH v2 02/24] iommu/amd: Drop IOVA cookie management Robin Murphy
2021-07-28 15:58   ` Robin Murphy
2021-07-28 15:58   ` Robin Murphy
2021-07-28 15:58 ` [PATCH v2 03/24] iommu/arm-smmu: " Robin Murphy
2021-07-28 15:58   ` Robin Murphy
2021-07-28 15:58   ` Robin Murphy
2021-07-28 15:58 ` [PATCH v2 04/24] iommu/vt-d: " Robin Murphy
2021-07-28 15:58   ` Robin Murphy
2021-07-28 15:58   ` Robin Murphy
2021-07-30  6:07   ` Lu Baolu
2021-07-30  6:07     ` Lu Baolu
2021-07-30  6:07     ` Lu Baolu
2021-07-28 15:58 ` [PATCH v2 05/24] iommu/exynos: " Robin Murphy
2021-07-28 15:58   ` Robin Murphy
2021-07-28 15:58   ` Robin Murphy
2021-07-28 15:58 ` [PATCH v2 06/24] iommu/ipmmu-vmsa: " Robin Murphy
2021-07-28 15:58   ` Robin Murphy
2021-07-28 15:58   ` Robin Murphy
2021-07-28 15:58 ` [PATCH v2 07/24] iommu/mtk: " Robin Murphy
2021-07-28 15:58   ` Robin Murphy
2021-07-28 15:58   ` Robin Murphy
2021-07-28 15:58 ` [PATCH v2 08/24] iommu/rockchip: " Robin Murphy
2021-07-28 15:58   ` Robin Murphy
2021-07-28 15:58   ` Robin Murphy
2021-07-28 15:58 ` [PATCH v2 09/24] iommu/sprd: " Robin Murphy
2021-07-28 15:58   ` Robin Murphy
2021-07-28 15:58   ` Robin Murphy
2021-07-28 15:58 ` [PATCH v2 10/24] iommu/sun50i: " Robin Murphy
2021-07-28 15:58   ` Robin Murphy
2021-07-28 15:58   ` Robin Murphy
2021-07-28 15:58 ` [PATCH v2 11/24] iommu/virtio: " Robin Murphy
2021-07-28 15:58   ` Robin Murphy
2021-07-28 15:58   ` Robin Murphy
2021-07-30  9:20   ` Jean-Philippe Brucker
2021-07-30  9:20     ` Jean-Philippe Brucker
2021-07-30  9:20     ` Jean-Philippe Brucker
2021-07-28 15:58 ` [PATCH v2 12/24] iommu/dma: Unexport " Robin Murphy
2021-07-28 15:58   ` Robin Murphy
2021-07-28 15:58   ` Robin Murphy
2021-07-30  6:07   ` Lu Baolu
2021-07-30  6:07     ` Lu Baolu
2021-07-30  6:07     ` Lu Baolu
2021-07-30  9:21   ` Jean-Philippe Brucker
2021-07-30  9:21     ` Jean-Philippe Brucker
2021-07-30  9:21     ` Jean-Philippe Brucker
2021-07-28 15:58 ` [PATCH v2 13/24] iommu/dma: Remove redundant "!dev" checks Robin Murphy
2021-07-28 15:58   ` Robin Murphy
2021-07-28 15:58   ` Robin Murphy
2021-07-30  6:08   ` Lu Baolu
2021-07-30  6:08     ` Lu Baolu
2021-07-30  6:08     ` Lu Baolu
2021-07-28 15:58 ` [PATCH v2 14/24] iommu: Introduce explicit type for non-strict DMA domains Robin Murphy
2021-07-28 15:58   ` Robin Murphy
2021-07-28 15:58   ` Robin Murphy
2021-07-30  6:08   ` Lu Baolu
2021-07-30  6:08     ` Lu Baolu
2021-07-30  6:08     ` Lu Baolu
2021-07-30  9:23   ` Jean-Philippe Brucker
2021-07-30  9:23     ` Jean-Philippe Brucker
2021-07-30  9:23     ` Jean-Philippe Brucker
2021-07-28 15:58 ` [PATCH v2 15/24] iommu/amd: Prepare for multiple DMA domain types Robin Murphy
2021-07-28 15:58   ` Robin Murphy
2021-07-28 15:58   ` Robin Murphy
2021-07-28 15:58 ` [PATCH v2 16/24] iommu/arm-smmu: " Robin Murphy
2021-07-28 15:58   ` Robin Murphy
2021-07-28 15:58   ` Robin Murphy
2021-07-28 15:58 ` [PATCH v2 17/24] iommu/vt-d: " Robin Murphy
2021-07-28 15:58   ` Robin Murphy
2021-07-28 15:58   ` Robin Murphy
2021-07-30  6:09   ` Lu Baolu
2021-07-30  6:09     ` Lu Baolu
2021-07-30  6:09     ` Lu Baolu
2021-07-28 15:58 ` [PATCH v2 18/24] iommu: Express DMA strictness via the domain type Robin Murphy
2021-07-28 15:58   ` Robin Murphy
2021-07-28 15:58   ` Robin Murphy
2021-07-29  7:13   ` Lu Baolu
2021-07-29  7:13     ` Lu Baolu
2021-07-29  7:13     ` Lu Baolu
2021-07-29  9:36     ` Robin Murphy
2021-07-29  9:36       ` Robin Murphy
2021-07-29  9:36       ` Robin Murphy
2021-07-29 12:42       ` Lu Baolu
2021-07-29 12:42         ` Lu Baolu
2021-07-29 12:42         ` Lu Baolu
2021-07-30  6:09       ` Lu Baolu
2021-07-30  6:09         ` Lu Baolu
2021-07-30  6:09         ` Lu Baolu
2021-07-28 15:58 ` [PATCH v2 19/24] iommu: Expose DMA domain strictness via sysfs Robin Murphy
2021-07-28 15:58   ` Robin Murphy
2021-07-28 15:58   ` Robin Murphy
2021-07-30  6:10   ` Lu Baolu
2021-07-30  6:10     ` Lu Baolu
2021-07-30  6:10     ` Lu Baolu
2021-07-30  9:28   ` Jean-Philippe Brucker [this message]
2021-07-30  9:28     ` Jean-Philippe Brucker
2021-07-30  9:28     ` Jean-Philippe Brucker
2021-07-30 10:20   ` John Garry
2021-07-30 10:20     ` John Garry
2021-07-30 10:20     ` John Garry
2021-07-28 15:58 ` [PATCH v2 20/24] iommu: Merge strictness and domain type configs Robin Murphy
2021-07-28 15:58   ` Robin Murphy
2021-07-28 15:58   ` Robin Murphy
2021-07-30  6:10   ` Lu Baolu
2021-07-30  6:10     ` Lu Baolu
2021-07-30  6:10     ` Lu Baolu
2021-07-30  9:29   ` Jean-Philippe Brucker
2021-07-30  9:29     ` Jean-Philippe Brucker
2021-07-30  9:29     ` Jean-Philippe Brucker
2021-07-30  9:33   ` John Garry
2021-07-30  9:33     ` John Garry
2021-07-30  9:33     ` John Garry
2021-07-28 15:58 ` [PATCH v2 21/24] iommu/dma: Factor out flush queue init Robin Murphy
2021-07-28 15:58   ` Robin Murphy
2021-07-28 15:58   ` Robin Murphy
2021-07-30  6:11   ` Lu Baolu
2021-07-30  6:11     ` Lu Baolu
2021-07-30  6:11     ` Lu Baolu
2021-07-30  9:20   ` John Garry
2021-07-30  9:20     ` John Garry
2021-07-30  9:20     ` John Garry
2021-07-28 15:58 ` [PATCH v2 22/24] iommu: Allow enabling non-strict mode dynamically Robin Murphy
2021-07-28 15:58   ` Robin Murphy
2021-07-28 15:58   ` Robin Murphy
2021-07-30  6:11   ` Lu Baolu
2021-07-30  6:11     ` Lu Baolu
2021-07-30  6:11     ` Lu Baolu
2021-07-30  9:24   ` John Garry
2021-07-30  9:24     ` John Garry
2021-07-30  9:24     ` John Garry
2021-07-28 15:58 ` [PATCH v2 23/24] iommu/arm-smmu: Allow non-strict in pgtable_quirks interface Robin Murphy
2021-07-28 15:58   ` Robin Murphy
2021-07-28 15:58   ` Robin Murphy
2021-08-02 13:04   ` Will Deacon
2021-08-02 13:04     ` Will Deacon
2021-08-02 13:04     ` Will Deacon
2021-08-02 14:15     ` Robin Murphy
2021-08-02 14:15       ` Robin Murphy
2021-08-02 14:15       ` Robin Murphy
2021-08-03 10:36       ` Will Deacon
2021-08-03 10:36         ` Will Deacon
2021-08-03 10:36         ` Will Deacon
2021-08-03 12:13         ` Robin Murphy
2021-08-03 12:13           ` Robin Murphy
2021-08-03 12:13           ` Robin Murphy
2021-08-03 12:35           ` Will Deacon
2021-08-03 12:35             ` Will Deacon
2021-08-03 12:35             ` Will Deacon
2021-07-28 15:58 ` [PATCH v2 24/24] iommu: Only log strictness for DMA domains Robin Murphy
2021-07-28 15:58   ` Robin Murphy
2021-07-28 15:58   ` Robin Murphy
2021-07-29  9:04   ` John Garry
2021-07-29  9:04     ` John Garry
2021-07-29  9:04     ` John Garry
2021-07-30  6:12   ` Lu Baolu
2021-07-30  6:12     ` Lu Baolu
2021-07-30  6:12     ` Lu Baolu
2021-07-29  2:55 ` [PATCH v2 00/24] iommu: Refactor DMA domain strictness chenxiang (M)
2021-07-29  2:55   ` chenxiang (M)
2021-07-29  2:55   ` chenxiang (M)
2021-07-29 10:59   ` Robin Murphy
2021-07-29 10:59     ` Robin Murphy
2021-07-29 10:59     ` Robin Murphy
2021-07-30  1:21     ` chenxiang (M)
2021-07-30  1:21       ` chenxiang (M)
2021-07-30  1:21       ` chenxiang (M)
2021-07-29 15:04 ` Heiko Stübner
2021-07-29 15:04   ` Heiko Stübner
2021-07-29 15:04   ` Heiko Stübner
2021-07-29 15:43   ` Robin Murphy
2021-07-29 15:43     ` Robin Murphy
2021-07-29 15:43     ` Robin Murphy
2021-07-29 15:53     ` Heiko Stübner
2021-07-29 15:53       ` Heiko Stübner
2021-07-29 15:53       ` Heiko Stübner
2021-07-29 16:29       ` Robin Murphy
2021-07-29 16:29         ` Robin Murphy
2021-07-29 16:29         ` Robin Murphy
2021-07-29 22:33 ` Doug Anderson
2021-07-29 22:33   ` Doug Anderson
2021-07-29 22:33   ` Doug Anderson
2021-07-30  0:06   ` Doug Anderson
2021-07-30  0:06     ` Doug Anderson
2021-07-30  0:06     ` Doug Anderson

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=YQPGNxhgVEagZ28H@myrica \
    --to=jean-philippe@linaro.org \
    --cc=dianders@chromium.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=joro@8bytes.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robin.murphy@arm.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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.