From: Mark Rutland <mark.rutland@arm.com>
To: Vladimir Murzin <vladimir.murzin@arm.com>
Cc: linux-arm-kernel@lists.infradead.org, catalin.marinas@arm.com,
will@kernel.org
Subject: Re: [PATCH] arm64: Clarify ARM64_WORKAROUND_REPEAT_TLBI semantics
Date: Fri, 3 Jul 2026 11:03:30 +0100 [thread overview]
Message-ID: <akeI8rsrkfLNs4Kb@J2N7QTR9R3> (raw)
In-Reply-To: <8d72230b-d636-447c-873e-b95304457a5a@arm.com>
On Mon, Jun 29, 2026 at 07:05:35PM +0100, Vladimir Murzin wrote:
> On 6/29/26 11:09, Mark Rutland wrote:
> > Will notes that the ARM64_WORKAROUND_REPEAT_TLBI name is potentially
> > misleading, and that it would be nice to rename that and add some
> > documentation. See:
> >
> > https://lore.kernel.org/linux-arm-kernel/ajKn_Pt50CmOUrsP@willie-the-truck/
> >
> > To that end, I've renamed the Kconfig symbol and hwcap from:
> >
> > [CONFIG_]ARM64_WORKAROUND_REPEAT_TLBI
> >
> > ... to:
> >
> > [CONFIG_]ARM64_WORKAROUND_REPEAT_TLBI_SYNC
> >
> > ... and I've added some rationale alongside the Kconfig. As the Kconfig
> > symbol isn't user selectable, the usual 'help' section won't appear in
> > menuconfig, so I've added this as a comment.
> >
>
> Although it won't appear in menuconfig, 3rd party tools that
> index config symbols may still consume the help section.
> I'm not sure how much we care about such tools...
FWIW, I'm happy either way -- I'll defer to Will's preference.
Mark.
prev parent reply other threads:[~2026-07-03 10:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 10:09 [PATCH] arm64: Clarify ARM64_WORKAROUND_REPEAT_TLBI semantics Mark Rutland
2026-06-29 18:05 ` Vladimir Murzin
2026-07-03 10:03 ` Mark Rutland [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=akeI8rsrkfLNs4Kb@J2N7QTR9R3 \
--to=mark.rutland@arm.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=vladimir.murzin@arm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox