From: Mark Rutland <mark.rutland@arm.com>
To: Fuad Tabba <tabba@google.com>
Cc: kvmarm@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
maz@kernel.org, oliver.upton@linux.dev, will@kernel.org,
joey.gouly@arm.com, suzuki.poulose@arm.com, yuzenghui@huawei.com,
catalin.marinas@arm.com, vdonnefort@google.com,
qperret@google.com, sebastianene@google.com, keirf@google.com,
smostafa@google.com
Subject: Re: [PATCH v3 1/3] arm64: sysreg: Fix and tidy up sysreg field definitions
Date: Fri, 29 Aug 2025 11:07:46 +0100 [thread overview]
Message-ID: <aLF78ux6oTQYKnHr@J2N7QTR9R3> (raw)
In-Reply-To: <20250829095143.123476-2-tabba@google.com>
On Fri, Aug 29, 2025 at 10:51:41AM +0100, Fuad Tabba wrote:
> Fix the value of ID_PFR1_EL1.Security NSACR_RFR to be 0b0010, as per
> DDI0601/2025-06, which wasn't correctly set when introduced in commit
> 1224308075f1 ("arm64/sysreg: Convert ID_PFR1_EL1 to automatic generation").
>
> While at it, remove redundant definitions of CPACR_EL12 and
> RCWSMASK_EL1 and fix some typos.
>
> Reviewed-by: Anshuman Khandual <anshuman.khandual@arm.com>
> Acked-by: Marc Zyngier <maz@kernel.org>
> Signed-off-by: Fuad Tabba <tabba@google.com>
> ---
> Note that NSACR_RFR isn't used in the kernel as far as I could tell, so
> I didn't add a 'Fixes' tag.
Since this is all cleanup, I think that's fine, but were that necessary,
it would be nicer to have the NSACR_RFR fix separate from the other
cleanups.
FWIW, as this stands:
Acked-by: Mark Rutland <mark.rutland@arm.com>
Mark.
> ---
> arch/arm64/tools/sysreg | 14 +++-----------
> 1 file changed, 3 insertions(+), 11 deletions(-)
>
> diff --git a/arch/arm64/tools/sysreg b/arch/arm64/tools/sysreg
> index 696ab1f32a67..f1a012ee0db6 100644
> --- a/arch/arm64/tools/sysreg
> +++ b/arch/arm64/tools/sysreg
> @@ -31,7 +31,7 @@
> # Mapping <name_EL1>
> # EndSysreg
>
> -# Where multiple system regsiters are not VHE aliases but share a
> +# Where multiple system registers are not VHE aliases but share a
> # common layout, a SysregFields block can be used to describe the
> # shared layout:
>
> @@ -54,7 +54,7 @@
> #
> # In general it is recommended that new enumeration items be named for the
> # feature that introduces them (eg, FEAT_LS64_ACCDATA introduces enumeration
> -# item ACCDATA) though it may be more taseful to do something else.
> +# item ACCDATA) though it may be more tasteful to do something else.
>
> Sysreg OSDTRRX_EL1 2 0 0 0 2
> Res0 63:32
> @@ -474,7 +474,7 @@ EndEnum
> Enum 7:4 Security
> 0b0000 NI
> 0b0001 EL3
> - 0b0001 NSACR_RFR
> + 0b0010 NSACR_RFR
> EndEnum
> UnsignedEnum 3:0 ProgMod
> 0b0000 NI
> @@ -2528,10 +2528,6 @@ Field 17:16 ZEN
> Res0 15:0
> EndSysreg
>
> -Sysreg CPACR_EL12 3 5 1 0 2
> -Mapping CPACR_EL1
> -EndSysreg
> -
> Sysreg CPACRALIAS_EL1 3 0 1 4 4
> Mapping CPACR_EL1
> EndSysreg
> @@ -2576,10 +2572,6 @@ Sysreg PFAR_EL12 3 5 6 0 5
> Mapping PFAR_EL1
> EndSysreg
>
> -Sysreg RCWSMASK_EL1 3 0 13 0 3
> -Field 63:0 RCWSMASK
> -EndSysreg
> -
> Sysreg SCTLR2_EL1 3 0 1 0 3
> Res0 63:13
> Field 12 CPTM0
> --
> 2.51.0.338.gd7d06c2dae-goog
>
>
next prev parent reply other threads:[~2025-08-29 14:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-29 9:51 [PATCH v3 0/3] arm64: sysreg: Fix sysreg field definitions and generation script Fuad Tabba
2025-08-29 9:51 ` [PATCH v3 1/3] arm64: sysreg: Fix and tidy up sysreg field definitions Fuad Tabba
2025-08-29 10:07 ` Mark Rutland [this message]
2025-08-29 9:51 ` [PATCH v3 2/3] arm64: sysreg: Correct sign definitions for EIESB and DoubleLock Fuad Tabba
2025-08-29 10:10 ` Mark Rutland
2025-08-29 9:51 ` [PATCH v3 3/3] arm64: sysreg: Add validation checks to sysreg header generation script Fuad Tabba
2025-08-29 10:14 ` Mark Rutland
2025-09-11 16:11 ` [PATCH v3 0/3] arm64: sysreg: Fix sysreg field definitions and " 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=aLF78ux6oTQYKnHr@J2N7QTR9R3 \
--to=mark.rutland@arm.com \
--cc=catalin.marinas@arm.com \
--cc=joey.gouly@arm.com \
--cc=keirf@google.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=qperret@google.com \
--cc=sebastianene@google.com \
--cc=smostafa@google.com \
--cc=suzuki.poulose@arm.com \
--cc=tabba@google.com \
--cc=vdonnefort@google.com \
--cc=will@kernel.org \
--cc=yuzenghui@huawei.com \
/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