From: Conor Dooley <conor@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
Conor Dooley <conor.dooley@microchip.com>,
Randy Dunlap <rdunlap@infradead.org>,
Jonathan Cameron <jonathan.cameron@huawei.com>,
Will Deacon <will@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] arm64, lib: make ARM64 select ARCH_HAS_CPU_CACHE_INVALIDATE_MEMREGION not GENERIC_CPU_CACHE_MAINTENANCE
Date: Thu, 20 Nov 2025 19:29:59 +0000 [thread overview]
Message-ID: <20251120-ruined-liability-9ecbf53affd1@spud> (raw)
In-Reply-To: <aR9QRuUigBsxxelm@arm.com>
[-- Attachment #1: Type: text/plain, Size: 1462 bytes --]
On Thu, Nov 20, 2025 at 05:30:46PM +0000, Catalin Marinas wrote:
> On Wed, Nov 19, 2025 at 07:08:27PM +0000, Conor Dooley wrote:
> > index 09aec4a1e13f..ac223e627bc5 100644
> > --- a/lib/Kconfig
> > +++ b/lib/Kconfig
> > @@ -544,8 +544,9 @@ config ARCH_HAS_CPU_CACHE_INVALIDATE_MEMREGION
> > bool
> >
> > config GENERIC_CPU_CACHE_MAINTENANCE
> > - bool
> > - select ARCH_HAS_CPU_CACHE_INVALIDATE_MEMREGION
> > + def_bool y
> > + depends on ARCH_HAS_CPU_CACHE_INVALIDATE_MEMREGION
> > + depends on ARM64
>
> That's what we do if GENERIC_CPU_CACHE_MAINTENANCE depends on some arch
> code but that's not the case here. GENERIC_CPU_CACHE_MAINTENANCE is an
> alternative implementation that an arch can select if it does not
> provide its own. I find the current code without the above patch better.
Right, I am going to leave it as-is for now then. That's both you and I
(and presumably Jonathan) finding the current form more natural. Sorry
Randy!
>
> Maybe what gets confusing here is that the core code uses
> ARCH_HAS_CPU_CACHE_INVALIDATE_MEMREGION directly. A more involved fix
> would be something like:
>
> config CPU_CACHE_INVALIDATE_MEMREGION
> def_bool y
> depends on ARCH_HAS_CPU_CACHE_INVALIDATE_MEMREGION ||
> GENERIC_CPU_CACHE_MAINTENANCE
>
> and then go and change all the uses of
> ARCH_HAS_CPU_CACHE_INVALIDATE_MEMREGION.
>
> Up to you, the current code also works for me.
>
> --
> Catalin
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-11-20 19:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-19 19:08 [PATCH v1] arm64, lib: make ARM64 select ARCH_HAS_CPU_CACHE_INVALIDATE_MEMREGION not GENERIC_CPU_CACHE_MAINTENANCE Conor Dooley
2025-11-19 21:22 ` Randy Dunlap
2025-11-20 17:30 ` Catalin Marinas
2025-11-20 19:29 ` Conor Dooley [this message]
2025-11-20 20:13 ` Randy Dunlap
2025-11-20 21:40 ` Catalin Marinas
2025-11-20 23:25 ` Randy Dunlap
2025-11-21 10:48 ` Jonathan Cameron
2025-11-21 18:44 ` Conor Dooley
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=20251120-ruined-liability-9ecbf53affd1@spud \
--to=conor@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=conor.dooley@microchip.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox