linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Garry <john.garry@huawei.com>
To: Zhen Lei <thunder.leizhen@huawei.com>,
	Jean-Philippe Brucker <jean-philippe.brucker@arm.com>,
	Robin Murphy <robin.murphy@arm.com>,
	"Will Deacon" <will.deacon@arm.com>,
	Joerg Roedel <joro@8bytes.org>,
	iommu <iommu@lists.linux-foundation.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Cc: Hanjun Guo <guohanjun@huawei.com>
Subject: Re: [PATCH 1/1] iommu: Add config option to set lazy mode as default
Date: Fri, 22 Mar 2019 14:42:57 +0000	[thread overview]
Message-ID: <8cf20613-7a9a-d4a1-b52e-4b526f2c7ff2@huawei.com> (raw)
In-Reply-To: <20190322141121.18428-1-thunder.leizhen@huawei.com>

On 22/03/2019 14:11, Zhen Lei wrote:

> This allows the default behaviour to be controlled by a kernel config
> option instead of changing the command line for the kernel to include
> "iommu.strict=0" on ARM64 where this is desired.
>
> This is similar to CONFIG_IOMMU_DEFAULT_PASSTHROUGH
>
> Note: At present, intel_iommu, amd_iommu and s390_iommu use lazy mode as
> defalut, so there is no need to add code for them.

/s/defalut/default/

>
> Signed-off-by: Zhen Lei <thunder.leizhen@huawei.com>
> ---
>  drivers/iommu/Kconfig | 14 ++++++++++++++
>  drivers/iommu/iommu.c |  5 +++++

Do we need to update kernel-parameters.txt for iommu.strict?

>  2 files changed, 19 insertions(+)
>
> diff --git a/drivers/iommu/Kconfig b/drivers/iommu/Kconfig
> index 6f07f3b21816c64..5ec9780f564eaf8 100644
> --- a/drivers/iommu/Kconfig
> +++ b/drivers/iommu/Kconfig
> @@ -85,6 +85,20 @@ config IOMMU_DEFAULT_PASSTHROUGH
>
>  	  If unsure, say N here.
>
> +config IOMMU_LAZY_MODE

maybe should add "DMA" to the name, and even "DEFAULT"

> +	bool "IOMMU use lazy mode to flush IOTLB and free IOVA"
> +	depends on IOMMU_API
> +	help
> +	  For every IOMMU unmap operation, the flush operation of IOTLB and the free
> +	  operation of IOVA are deferred.

This is a bit unclear, as there is no context. I think that you need to 
say something like, "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. Removing the need to pass in iommu.strict=0
> +	  through command line on ARM64(Now, intel_iommu, amd_iommu, s390_iommu use
> +	  lazy mode as deault).

prone to going out-of-date

  If this is enabled, you can still disable with kernel
> +	  parameters, such as iommu.strict=1, intel_iommu=strict, amd_iommu=fullflush
> +	  or s390_iommu=strict depending on the architecture.
> +
> +	  If unsure, say N here.
> +
>  config OF_IOMMU
>         def_bool y
>         depends on OF && IOMMU_API
> diff --git a/drivers/iommu/iommu.c b/drivers/iommu/iommu.c
> index 33a982e33716369..e307d70d1578b3b 100644
> --- a/drivers/iommu/iommu.c
> +++ b/drivers/iommu/iommu.c
> @@ -43,7 +43,12 @@
>  #else
>  static unsigned int iommu_def_domain_type = IOMMU_DOMAIN_DMA;
>  #endif
> +
> +#ifdef CONFIG_IOMMU_LAZY_MODE
> +static bool iommu_dma_strict __read_mostly;
> +#else
>  static bool iommu_dma_strict __read_mostly = true;
> +#endif
>
>  struct iommu_callback_data {
>  	const struct iommu_ops *ops;
> --
> 1.8.3
>
>
>

Cheers




  reply	other threads:[~2019-03-22 14:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-22 14:11 [PATCH 1/1] iommu: Add config option to set lazy mode as default Zhen Lei
2019-03-22 14:42 ` John Garry [this message]
2019-03-25  2:21   ` Leizhen (ThunderTown)

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=8cf20613-7a9a-d4a1-b52e-4b526f2c7ff2@huawei.com \
    --to=john.garry@huawei.com \
    --cc=guohanjun@huawei.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=jean-philippe.brucker@arm.com \
    --cc=joro@8bytes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=thunder.leizhen@huawei.com \
    --cc=will.deacon@arm.com \
    /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 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).