From: Will Deacon <will@kernel.org>
To: Ryan Roberts <ryan.roberts@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Ard Biesheuvel <ardb@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Oliver Upton <oliver.upton@linux.dev>,
Marc Zyngier <maz@kernel.org>
Subject: Re: [PATCH 00/10] arm64: Replace TLB invalidation preprocessor macros with C functions
Date: Sat, 13 Dec 2025 05:13:40 +0900 [thread overview]
Message-ID: <aTx3dM8XUMQMOf2-@google.com> (raw)
In-Reply-To: <b40ee164-f533-43da-a4e2-068c9ae1e771@arm.com>
On Fri, Dec 12, 2025 at 12:12:05PM +0000, Ryan Roberts wrote:
> On 10/12/2025 12:29, Ryan Roberts wrote:
> > On 11/07/2025 17:17, Will Deacon wrote:
> >> I cooked this series following a complaint from Linus back in March
> >> about our range-based TLB invalidation macro after we fixed an
> >> over-invalidation bug thanks to incorrect handling of its arguments:
> >>
> >> https://lore.kernel.org/all/CAHk-=wgiX0q0WCL+SFwVCYtG7JR3=2Rshse-5J3AO2Y4AgT7Jw@mail.gmail.com/
> >>
> >> Once I started trying to rework the range macro into a C function, I
> >> spotted a few other opportunities for cleanup and so I've ended up with
> >> this series.
> >>
> >> Testing and feedback welcome.
> >
> > Hi Will,
> >
> > Did this go anywhere/are you planning to post a new version? There are a couple
> > of other cleanups I'd like to do in this area, and also I'd like to add tlbip
> > support. But I don't want to spend time on it if the baseline is going to
> > drastically change.
> >
> > If you're not planning a v2, perhaps I could have a go then extend for the
> > extras I want to do?
>
> Since I didn't hear back, I've reworked the series to include Linus's suggestion
> and am currently testing. Plan to post against -rc1.
Sorry, at LPC atm and have fallen behind. I was still planning to rework
this but I'm aware of other folks at Arm making changes here as well so
you should be wary of that too.
Regardless of macros or indirect branches, I was relatively happy with
some of the cleanup that fell out of this series so I'd be keen to land
it either way.
Will
prev parent reply other threads:[~2025-12-12 20:13 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-11 16:17 [PATCH 00/10] arm64: Replace TLB invalidation preprocessor macros with C functions Will Deacon
2025-07-11 16:17 ` [PATCH 01/10] arm64: mm: Introduce a C wrapper for by-level TLB invalidation helpers Will Deacon
2025-07-14 8:38 ` Ryan Roberts
2025-07-11 16:17 ` [PATCH 02/10] arm64: mm: Introduce a C wrapper for by-range " Will Deacon
2025-07-14 8:26 ` Ryan Roberts
2025-07-11 16:17 ` [PATCH 03/10] arm64: mm: Implicitly invalidate user ASID based on TLBI operation Will Deacon
2025-07-14 8:44 ` Ryan Roberts
2025-07-14 9:46 ` Ryan Roberts
2025-07-11 16:17 ` [PATCH 04/10] arm64: mm: Remove unused 'tlbi_user' argument from __flush_tlb_range_op() Will Deacon
2025-07-11 16:17 ` [PATCH 05/10] arm64: mm: Re-implement the __tlbi_level macro in C Will Deacon
2025-07-14 9:02 ` Ryan Roberts
2025-07-11 16:17 ` [PATCH 06/10] arm64: mm: Simplify __TLBI_RANGE_NUM() macro Will Deacon
2025-07-14 9:06 ` Ryan Roberts
2025-07-15 5:13 ` Dev Jain
2025-07-11 16:17 ` [PATCH 07/10] arm64: mm: Push __TLBI_VADDR() into __tlbi_level() Will Deacon
2025-07-11 16:17 ` [PATCH 08/10] arm64: mm: Inline __TLBI_VADDR_RANGE() into __tlbi_range() Will Deacon
2025-07-14 9:17 ` Ryan Roberts
2025-07-11 16:17 ` [PATCH 09/10] arm64: mm: Simplify __flush_tlb_range_limit_excess() Will Deacon
2025-07-14 9:30 ` Ryan Roberts
2025-07-15 5:38 ` Dev Jain
2025-07-11 16:17 ` [PATCH 10/10] arm64: mm: Re-implement the __flush_tlb_range_op macro in C Will Deacon
2025-07-11 18:16 ` Linus Torvalds
2025-07-13 13:35 ` Will Deacon
2025-07-14 9:44 ` Ryan Roberts
2025-12-10 12:29 ` [PATCH 00/10] arm64: Replace TLB invalidation preprocessor macros with C functions Ryan Roberts
2025-12-12 12:12 ` Ryan Roberts
2025-12-12 20:13 ` 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=aTx3dM8XUMQMOf2-@google.com \
--to=will@kernel.org \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=ryan.roberts@arm.com \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).