From: Catalin Marinas <catalin.marinas@arm.com>
To: Piotr Jaroszynski <pjaroszynski@nvidia.com>
Cc: Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org,
Robin Murphy <robin.murphy@arm.com>,
Alistair Popple <apopple@nvidia.com>,
Raghavendra Rao Ananta <rananta@google.com>,
SeongJae Park <sj@kernel.org>, Jason Gunthorpe <jgg@nvidia.com>,
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
Subject: Re: [PATCH] [arm64/tlb] Fix mmu notifiers for range-based invalidates
Date: Wed, 5 Mar 2025 18:48:19 +0000 [thread overview]
Message-ID: <Z8iccxCo7tkqvE_p@arm.com> (raw)
In-Reply-To: <20250304085127.2238030-1-pjaroszynski@nvidia.com>
On Tue, Mar 04, 2025 at 12:51:27AM -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.
>
> This has been broken since commit 6bbd42e2df8f ("mmu_notifiers: call
> invalidate_range() when invalidating TLBs") when the call to the
> notifiers was added to __flush_tlb_range(). It predates the addition of
> the __flush_tlb_range_op() macro from commit 360839027a6e ("arm64: tlb:
> Refactor the core flush algorithm of __flush_tlb_range") that made the
> bug hard to spot.
That's the problem with macros.
Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
Will, do you want to take this as a fix? It's only a performance
regression, though you never know how it breaks the callers of the macro
at some point.
> Fixes: 6bbd42e2df8f ("mmu_notifiers: call invalidate_range() when invalidating TLBs")
>
> Signed-off-by: Piotr Jaroszynski <pjaroszynski@nvidia.com>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Will Deacon <will@kernel.org>
> Cc: Robin Murphy <robin.murphy@arm.com>
> Cc: Alistair Popple <apopple@nvidia.com>
> Cc: Raghavendra Rao Ananta <rananta@google.com>
> Cc: SeongJae Park <sj@kernel.org>
> Cc: Jason Gunthorpe <jgg@nvidia.com>
> Cc: John Hubbard <jhubbard@nvidia.com>
> Cc: Nicolin Chen <nicolinc@nvidia.com>
> Cc: linux-arm-kernel@lists.infradead.org
> Cc: iommu@lists.linux.dev
> Cc: linux-mm@kvack.org
> Cc: linux-kernel@vger.kernel.org
> Cc: stable@vger.kernel.org
> ---
> arch/arm64/include/asm/tlbflush.h | 22 ++++++++++++----------
> 1 file changed, 12 insertions(+), 10 deletions(-)
>
> diff --git a/arch/arm64/include/asm/tlbflush.h b/arch/arm64/include/asm/tlbflush.h
> index bc94e036a26b..8104aee4f9a0 100644
> --- a/arch/arm64/include/asm/tlbflush.h
> +++ b/arch/arm64/include/asm/tlbflush.h
> @@ -396,33 +396,35 @@ static inline void arch_tlbbatch_flush(struct arch_tlbflush_unmap_batch *batch)
> #define __flush_tlb_range_op(op, start, pages, stride, \
> asid, tlb_level, tlbi_user, lpa2) \
> do { \
> + typeof(start) __flush_start = start; \
> + typeof(pages) __flush_pages = pages; \
> int num = 0; \
> int scale = 3; \
> int shift = lpa2 ? 16 : PAGE_SHIFT; \
> unsigned long addr; \
> \
> - while (pages > 0) { \
> + while (__flush_pages > 0) { \
> if (!system_supports_tlb_range() || \
> - pages == 1 || \
> - (lpa2 && start != ALIGN(start, SZ_64K))) { \
> - addr = __TLBI_VADDR(start, asid); \
> + __flush_pages == 1 || \
> + (lpa2 && __flush_start != ALIGN(__flush_start, SZ_64K))) { \
> + addr = __TLBI_VADDR(__flush_start, asid); \
> __tlbi_level(op, addr, tlb_level); \
> if (tlbi_user) \
> __tlbi_user_level(op, addr, tlb_level); \
> - start += stride; \
> - pages -= stride >> PAGE_SHIFT; \
> + __flush_start += stride; \
> + __flush_pages -= stride >> PAGE_SHIFT; \
> continue; \
> } \
> \
> - num = __TLBI_RANGE_NUM(pages, scale); \
> + num = __TLBI_RANGE_NUM(__flush_pages, scale); \
> if (num >= 0) { \
> - addr = __TLBI_VADDR_RANGE(start >> shift, asid, \
> + addr = __TLBI_VADDR_RANGE(__flush_start >> shift, asid, \
> scale, num, tlb_level); \
> __tlbi(r##op, addr); \
> if (tlbi_user) \
> __tlbi_user(r##op, addr); \
> - start += __TLBI_RANGE_PAGES(num, scale) << PAGE_SHIFT; \
> - pages -= __TLBI_RANGE_PAGES(num, scale); \
> + __flush_start += __TLBI_RANGE_PAGES(num, scale) << PAGE_SHIFT; \
> + __flush_pages -= __TLBI_RANGE_PAGES(num, scale);\
> } \
> scale--; \
> } \
>
> base-commit: 99fa936e8e4f117d62f229003c9799686f74cebc
> --
> 2.22.1.7.gac84d6e93c.dirty
--
Catalin
next prev parent reply other threads:[~2025-03-05 18:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 8:51 [PATCH] [arm64/tlb] Fix mmu notifiers for range-based invalidates Piotr Jaroszynski
2025-03-05 18:48 ` Catalin Marinas [this message]
2025-03-05 19:35 ` Will Deacon
2025-03-05 23:49 ` Alistair Popple
2025-03-11 13:13 ` Will Deacon
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=Z8iccxCo7tkqvE_p@arm.com \
--to=catalin.marinas@arm.com \
--cc=apopple@nvidia.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=jhubbard@nvidia.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 \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.