From: Richard Henderson <richard.henderson@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>,
qemu-arm@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH] target/arm: Don't implement *32_EL2 registers when EL1 is AArch64 only
Date: Tue, 21 Nov 2023 12:39:13 -0600 [thread overview]
Message-ID: <8b3fe672-d7cb-46d0-87d6-2c89a0d3f272@linaro.org> (raw)
In-Reply-To: <20231121144605.3980419-1-peter.maydell@linaro.org>
On 11/21/23 08:46, Peter Maydell wrote:
> The system registers DBGVCR32_EL2, FPEXC32_EL2, DACR32_EL2 and
> IFSR32_EL2 are present only to allow an AArch64 EL2 or EL3 to read
> and write the contents of an AArch32-only system register. The
> architecture requires that they are present only when EL1 can be
> AArch32, but we implement them unconditionally. This was OK when all
> our CPUs supported AArch32 EL1, but we have quite a lot of CPU models
> now which only support AArch64 at EL1:
> a64fx
> cortex-a76
> cortex-a710
> neoverse-n1
> neoverse-n2
> neoverse-v1
>
> Only define these registers for CPUs which allow AArch32 EL1.
>
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> ---
> I happened to notice this reading through the Arm ARM recently. This
> is technically a bug, but you'll only notice it if you deliberately
> look at what should be an unimplemented register to see if it UNDEFs,
> so I don't think it's worth either putting in 8.2 or backporting to
> stable.
> ---
> target/arm/debug_helper.c | 23 +++++++++++++++--------
> target/arm/helper.c | 35 +++++++++++++++++++++--------------
> 2 files changed, 36 insertions(+), 22 deletions(-)
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
r~
prev parent reply other threads:[~2023-11-21 18:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 14:46 [PATCH] target/arm: Don't implement *32_EL2 registers when EL1 is AArch64 only Peter Maydell
2023-11-21 18:39 ` Richard Henderson [this message]
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=8b3fe672-d7cb-46d0-87d6-2c89a0d3f272@linaro.org \
--to=richard.henderson@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).