From: Catalin Marinas <catalin.marinas@arm.com>
To: Fuad Tabba <fuad.tabba@linux.dev>
Cc: Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Marc Zyngier <maz@kernel.org>, Oliver Upton <oupton@kernel.org>,
Anshuman Khandual <anshuman.khandual@arm.com>,
"Rob Herring (Arm)" <robh@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64/boot: Don't set PMUv3p9 FGT2 bits without PMUv3
Date: Fri, 2 Oct 2026 16:39:37 +0100 [thread overview]
Message-ID: <ar_QOXqCYTGargBe@arm.com> (raw)
In-Reply-To: <CA+EHjTzemfoX9e8Ppw+AcuUpNND_CipLCUM9xgid1eYXmV=jzg@mail.gmail.com>
On Fri, Oct 02, 2026 at 04:24:06PM +0100, Fuad Tabba wrote:
> On Fri, Oct 02, 2026 at 03:51:16PM +0100, Catalin Marinas wrote:
> > I couldn't figure out the #8 either. I wonder whether it's more readable
> > as (untested):
> >
> > sub x1, x1, #ID_AA64DFR0_EL1_PMUVer_V3P9
> > cmp x1, #(ID_AA64DFR0_EL1_PMUVer_IMP_DEF - ID_AA64DFR0_EL1_PMUVer_V3P9)
> > b.hs .Lskip_pmuv3p9_\@ // Skip unless V3P9 <= PMUVer < IMP_DEF
>
> This looks correct to me.
>
> That said, if readability is the goal, I think the plainest is two
> compares and two branches. It's one more instruction, but this runs
> once at boot:
>
> cmp x1, #ID_AA64DFR0_EL1_PMUVer_IMP_DEF
> b.eq .Lskip_pmuv3p9_\@
> cmp x1, #ID_AA64DFR0_EL1_PMUVer_V3P9
> b.lt .Lskip_pmuv3p9_\@
>
> I used ccmp to match __init_el2_debug in the same file, which does the
> same NI/IMP_DEF check with a raw #4, as does reset_pmuserenr_el0 in
> assembler.h (and hyp-entry.S uses the same pattern for HVC64/HVC32).
I'll leave it to Will. My preference is whatever is more readable, no
need to optimise another cycle or two here.
--
Catalin
next prev parent reply other threads:[~2026-10-02 15:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 12:12 [PATCH] arm64/boot: Don't set PMUv3p9 FGT2 bits without PMUv3 Fuad Tabba
2026-09-30 13:26 ` Anshuman Khandual
2026-09-30 13:32 ` Fuad Tabba
2026-10-01 2:59 ` Anshuman Khandual
2026-10-02 13:29 ` Will Deacon
2026-10-02 13:54 ` Fuad Tabba
2026-10-02 14:00 ` Will Deacon
2026-10-02 14:51 ` Catalin Marinas
2026-10-02 15:24 ` Fuad Tabba
2026-10-02 15:39 ` Catalin Marinas [this message]
2026-10-04 8:39 ` Will Deacon
2026-10-04 13:39 ` Fuad Tabba
2026-10-02 15:33 ` Bradley Morgan
2026-10-04 13:45 ` 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=ar_QOXqCYTGargBe@arm.com \
--to=catalin.marinas@arm.com \
--cc=anshuman.khandual@arm.com \
--cc=fuad.tabba@linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=oupton@kernel.org \
--cc=robh@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.