From: Will Deacon <will@kernel.org>
To: Robin Murphy <robin.murphy@arm.com>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>,
jean-philippe@linaro.org, linux-arm-kernel@lists.infradead.org,
joro@8bytes.org, iommu@lists.linux.dev
Subject: Re: [PATCH] iommu/arm-smmu-v3: Set TTL invalidation hint better
Date: Thu, 8 Jun 2023 22:36:05 +0100 [thread overview]
Message-ID: <168625802263.628430.15833629790497414818.b4-ty@kernel.org> (raw)
In-Reply-To: <b409d9a17c52dc0db51faee91d92737bb7975f5b.1685637456.git.robin.murphy@arm.com>
On Thu, 1 Jun 2023 17:43:33 +0100, Robin Murphy wrote:
> When io-pgtable unmaps a whole table, rather than waste time walking it
> to find the leaf entries to invalidate exactly, it simply expects
> .tlb_flush_walk with nominal last-level granularity to invalidate any
> leaf entries at higher intermediate levels as well. This works fine with
> page-based invalidation, but with range commands we need to be careful
> with the TTL hint - unconditionally setting it based on the given level
> 3 granule means that an invalidation for a level 1 table would strictly
> not be required to affect level 2 block entries. It's easy to comply
> with the expected behaviour by simply not setting the TTL hint for
> non-leaf invalidations, so let's do that.
>
> [...]
Applied to will (for-joerg/arm-smmu/updates), thanks!
[1/1] iommu/arm-smmu-v3: Set TTL invalidation hint better
https://git.kernel.org/will/c/6833b8f2e199
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2023-06-08 21:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 16:43 [PATCH] iommu/arm-smmu-v3: Set TTL invalidation hint better Robin Murphy
2023-06-08 21:36 ` Will Deacon [this message]
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=168625802263.628430.15833629790497414818.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=iommu@lists.linux.dev \
--cc=jean-philippe@linaro.org \
--cc=joro@8bytes.org \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=robin.murphy@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).