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 2/3] arm64: sysreg: Correct sign definitions for EIESB and DoubleLock
Date: Fri, 29 Aug 2025 11:10:45 +0100 [thread overview]
Message-ID: <aLF8pU4k5chetsDy@J2N7QTR9R3> (raw)
In-Reply-To: <20250829095143.123476-3-tabba@google.com>
On Fri, Aug 29, 2025 at 10:51:42AM +0100, Fuad Tabba wrote:
> The `ID_AA64MMFR4_EL1.EIESB` field, is an unsigned enumeration, but was
> incorrectly defined as a `SignedEnum` when introduced in commit
> cfc680bb04c5 ("arm64: sysreg: Add layout for ID_AA64MMFR4_EL1"). This is
> corrected to `UnsignedEnum`.
>
> Conversely, the `ID_AA64DFR0_EL1.DoubleLock` field, is a signed
> enumeration, but was incorrectly defined as an `UnsignedEnum`. This is
> corrected to `SignedEnum`, which wasn't correctly set when annotated as
> such in commit ad16d4cf0b4f ("arm64/sysreg: Initial unsigned annotations
> for ID registers").
>
> Signed-off-by: Fuad Tabba <tabba@google.com>
> ---
> Note: No active users in the kernel for these two fields yet. pKVM
> checks DoubleLock, but only for protected VMs, which aren't enabled
> upstream yet. Hence no Fixes tag.
I have no strong feelings either way on that, so FWIW:
Acked-by: Mark Rutland <mark.rutland@arm.com>
Mark.
> ---
> arch/arm64/tools/sysreg | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm64/tools/sysreg b/arch/arm64/tools/sysreg
> index f1a012ee0db6..d396fa587ec1 100644
> --- a/arch/arm64/tools/sysreg
> +++ b/arch/arm64/tools/sysreg
> @@ -1693,7 +1693,7 @@ UnsignedEnum 43:40 TraceFilt
> 0b0000 NI
> 0b0001 IMP
> EndEnum
> -UnsignedEnum 39:36 DoubleLock
> +SignedEnum 39:36 DoubleLock
> 0b0000 IMP
> 0b1111 NI
> EndEnum
> @@ -2409,7 +2409,7 @@ UnsignedEnum 11:8 ASID2
> 0b0000 NI
> 0b0001 IMP
> EndEnum
> -SignedEnum 7:4 EIESB
> +UnsignedEnum 7:4 EIESB
> 0b0000 NI
> 0b0001 ToEL3
> 0b0010 ToELx
> --
> 2.51.0.338.gd7d06c2dae-goog
>
>
next prev parent reply other threads:[~2025-08-29 14:49 UTC|newest]
Thread overview: 7+ 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
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 [this message]
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
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=aLF8pU4k5chetsDy@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;
as well as URLs for NNTP newsgroup(s).