[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1e95deac-b0c3-e122-f1e5-7748424a2c9f@huawei.com>
Date: Mon, 14 Jun 2021 17:29:31 +0100
From: John Garry <john.garry@...wei.com>
To: Robin Murphy <robin.murphy@....com>, <joro@...tes.org>
CC: <will@...nel.org>, <iommu@...ts.linux-foundation.org>,
<linux-kernel@...r.kernel.org>, <baolu.lu@...ux.intel.com>
Subject: Re: [PATCH] iommu: Update "iommu.strict" documentation
On 14/06/2021 15:57, Robin Murphy wrote:
> Consolidating the flush queue logic also meant that the "iommu.strict"
> option started taking effect on x86 as well. Make sure we document that.
>
> Fixes: a250c23f15c2 ("iommu: remove DOMAIN_ATTR_DMA_USE_FLUSH_QUEUE")
> Signed-off-by: Robin Murphy <robin.murphy@....com>
I assumed that all bets were off when we use a cmdline param which is
not "officially" supported.
Anyway, FWIW:
Reviewed-by: John Garry <john.garry@...wei.com>
> ---
> Documentation/admin-guide/kernel-parameters.txt | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
> index cb89dbdedc46..20a32de990ed 100644
> --- a/Documentation/admin-guide/kernel-parameters.txt
> +++ b/Documentation/admin-guide/kernel-parameters.txt
> @@ -1987,7 +1987,7 @@
> forcing Dual Address Cycle for PCI cards supporting
> greater than 32-bit addressing.
>
> - iommu.strict= [ARM64] Configure TLB invalidation behaviour
> + iommu.strict= [ARM64, X86] Configure TLB invalidation behaviour
> Format: { "0" | "1" }
> 0 - Lazy mode.
> Request that DMA unmap operations use deferred
Powered by blists - more mailing lists