From: Will Deacon <will@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>,
linux-arm-kernel@lists.infradead.org,
Piotr Jaroszynski <pjaroszynski@nvidia.com>
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Alistair Popple <apopple@nvidia.com>,
Raghavendra Rao Ananta <rananta@google.com>,
SeongJae Park <sj@kernel.org>, John Hubbard <jhubbard@nvidia.com>,
Nicolin Chen <nicolinc@nvidia.com>,
iommu@lists.linux.dev, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Jason Gunthorpe <jgg@ziepe.ca>
Subject: Re: [PATCH] [arm64/tlb] Fix mmu notifiers for range-based invalidates
Date: Tue, 11 Mar 2025 13:13:36 +0000 [thread overview]
Message-ID: <174169306404.278141.17801949874773526998.b4-ty@kernel.org> (raw)
In-Reply-To: <20250304085127.2238030-1-pjaroszynski@nvidia.com>
On Tue, 04 Mar 2025 00:51:27 -0800, Piotr Jaroszynski wrote:
> Update the __flush_tlb_range_op macro not to modify its parameters as
> these are unexepcted semantics. In practice, this fixes the call to
> mmu_notifier_arch_invalidate_secondary_tlbs() in
> __flush_tlb_range_nosync() to use the correct range instead of an empty
> range with start=end. The empty range was (un)lucky as it results in
> taking the invalidate-all path that doesn't cause correctness issues,
> but can certainly result in suboptimal perf.
>
> [...]
Applied to arm64 (for-next/fixes), thanks!
[1/1] Fix mmu notifiers for range-based invalidates
https://git.kernel.org/arm64/c/f7edb07ad7c6
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
next prev parent reply other threads:[~2025-03-11 13:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 8:51 Piotr Jaroszynski
2025-03-05 18:48 ` Catalin Marinas
2025-03-05 19:35 ` Will Deacon
2025-03-05 23:49 ` Alistair Popple
2025-03-11 13:13 ` Will Deacon [this message]
2025-03-17 13:07 ` Ivan T. Ivanov
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=174169306404.278141.17801949874773526998.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=apopple@nvidia.com \
--cc=catalin.marinas@arm.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=jhubbard@nvidia.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nicolinc@nvidia.com \
--cc=pjaroszynski@nvidia.com \
--cc=rananta@google.com \
--cc=robin.murphy@arm.com \
--cc=sj@kernel.org \
--cc=stable@vger.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