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,