From: John Garry <john.garry@huawei.com>
To: Robin Murphy <robin.murphy@arm.com>, <joro@8bytes.org>
Cc: <will@kernel.org>, <iommu@lists.linux-foundation.org>,
<linux-kernel@vger.kernel.org>, <baolu.lu@linux.intel.com>
Subject: Re: [PATCH] iommu: Update "iommu.strict" documentation
Date: Mon, 14 Jun 2021 17:29:31 +0100 [thread overview]
Message-ID: <1e95deac-b0c3-e122-f1e5-7748424a2c9f@huawei.com> (raw)
In-Reply-To: <2c8c06e1b449d6b060c5bf9ad3b403cd142f405d.1623682646.git.robin.murphy@arm.com>
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@arm.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@huawei.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
next prev parent reply other threads:[~2021-06-14 16:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-14 14:57 Robin Murphy
2021-06-14 16:29 ` John Garry [this message]
2021-06-15 7:05 ` Lu Baolu
2021-06-17 15:04 ` Joerg Roedel
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=1e95deac-b0c3-e122-f1e5-7748424a2c9f@huawei.com \
--to=john.garry@huawei.com \
--cc=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®