From: Linu Cherian <linu.cherian@arm.com>
To: Will Deacon <will@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Ryan Roberts <ryan.roberts@arm.com>,
Kevin Brodsky <kevin.brodsky@arm.com>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Gavin Shan <gshan@redhat.com>
Subject: Re: [PATCH v4 5/6] arm64: cpufeature: Rename BBML2_NOABORT as BBML3
Date: Fri, 7 Aug 2026 08:02:59 +0530 [thread overview]
Message-ID: <anVD26jl4Ve63FqA@a079125.arm.com> (raw)
In-Reply-To: <anTARBCJZ6N-ppaO@willie-the-truck>
On Thu, Aug 06, 2026 at 06:11:32PM +0100, Will Deacon wrote:
> On Thu, Jul 23, 2026 at 10:10:32AM +0530, Linu Cherian wrote:
> > - As bbml2_noabort is functionally equivalent to bbml3,
> > rename cpu/system_supports_bbml2_noabort to
> > cpu/system_supports_bbml3.
> > The ARM64 capability name is also renamed accordingly.
> >
> > - As BBML2_NOABORT or the equivalent BBML3 is the
> > kernel requirement for setting up linear map with
> > block/contpte mappings and not BBML2, replace all
> > bbml2 references with bbml3.
> >
> > FEAT_BBML3, is introduced as part of 2025 Architecture Extensions.
> > https://developer.arm.com/documentation/109697/2026_03/2025-Architecture-Extensions
> >
> > No functional changes are introduced with this patch.
> >
> > Reviewed-by: Gavin Shan <gshan@redhat.com>
> > Reviewed-by: Anshuman Khandual <anshuman.khandual@arm.com>
> > Signed-off-by: Linu Cherian <linu.cherian@arm.com>
> > ---
> > arch/arm64/include/asm/cpufeature.h | 6 ++--
> > arch/arm64/kernel/cpufeature.c | 30 +++++-----------
> > arch/arm64/mm/contpte.c | 21 +++++------
> > arch/arm64/mm/mmu.c | 54 ++++++++++++++---------------
> > arch/arm64/mm/proc.S | 4 +--
> > arch/arm64/tools/cpucaps | 2 +-
> > 6 files changed, 50 insertions(+), 67 deletions(-)
>
> This breaks the build because you haven't updated the caller in the SMMUv3
> SVA code.
>
> I'll push a fix on top...
Yeah, i missed that. Thanks for pointing out and the fix.
>
> Will
next prev parent reply other threads:[~2026-08-07 2:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 4:40 [PATCH v4 0/6] Add BBML3 cpu feature Linu Cherian
2026-07-23 4:40 ` [PATCH v4 1/6] arm64: cputype: Add Cortex-A520AE definitions Linu Cherian
2026-07-23 4:40 ` [PATCH v4 2/6] arm64: cputype: Add C1-Nano definitions Linu Cherian
2026-07-23 4:40 ` [PATCH v4 3/6] arm64: cpufeature: Extend bbml2_noabort support list Linu Cherian
2026-07-23 7:26 ` Anshuman Khandual
2026-07-23 4:40 ` [PATCH v4 4/6] arm64: sysreg: Add BBM_3 Linu Cherian
2026-07-23 4:40 ` [PATCH v4 5/6] arm64: cpufeature: Rename BBML2_NOABORT as BBML3 Linu Cherian
2026-08-06 17:11 ` Will Deacon
2026-08-07 2:32 ` Linu Cherian [this message]
2026-07-23 4:40 ` [PATCH v4 6/6] arm64: cpufeature: Detect BBML3 based on ID_AA64MMFR2_EL1.BBM Linu Cherian
2026-07-31 15:13 ` Will Deacon
2026-08-03 3:52 ` Linu Cherian
2026-08-03 4:19 ` Anshuman Khandual
2026-08-04 13:51 ` Will Deacon
2026-08-05 9:20 ` Linu Cherian
2026-08-06 11:26 ` Will Deacon
2026-08-06 17:11 ` [PATCH v4 0/6] Add BBML3 cpu feature Will Deacon
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=anVD26jl4Ve63FqA@a079125.arm.com \
--to=linu.cherian@arm.com \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=gshan@redhat.com \
--cc=kevin.brodsky@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=ryan.roberts@arm.com \
--cc=suzuki.poulose@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