[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <174169306404.278141.17801949874773526998.b4-ty@kernel.org>
Date: Tue, 11 Mar 2025 13:13:36 +0000
From: Will Deacon <will@...nel.org>
To: Catalin Marinas <catalin.marinas@....com>,
linux-arm-kernel@...ts.infradead.org,
Piotr Jaroszynski <pjaroszynski@...dia.com>
Cc: kernel-team@...roid.com,
Will Deacon <will@...nel.org>,
Robin Murphy <robin.murphy@....com>,
Alistair Popple <apopple@...dia.com>,
Raghavendra Rao Ananta <rananta@...gle.com>,
SeongJae Park <sj@...nel.org>,
John Hubbard <jhubbard@...dia.com>,
Nicolin Chen <nicolinc@...dia.com>,
iommu@...ts.linux.dev,
linux-mm@...ck.org,
linux-kernel@...r.kernel.org,
stable@...r.kernel.org,
Jason Gunthorpe <jgg@...pe.ca>
Subject: Re: [PATCH] [arm64/tlb] Fix mmu notifiers for range-based invalidates
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
Powered by blists - more mailing lists