From: Richard Henderson <richard.henderson@linaro.org>
To: qemu-devel@nongnu.org
Subject: Re: [RFC PATCH] target/arm: clamp value to account for RES0 fields
Date: Tue, 17 Jun 2025 19:13:16 -0700 [thread overview]
Message-ID: <c0bbe37c-f926-4425-9cc8-7719035bc06a@linaro.org> (raw)
In-Reply-To: <20250616201042.2196127-1-alex.bennee@linaro.org>
On 6/16/25 13:10, Alex Bennée wrote:
> If the user writes a large value to the register but with the bottom
> bits unset we could end up with something illegal. By clamping ahead
> of the check we at least assure we won't assert(bpr > 0) later in the
> GIC interface code.
>
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> ---
> hw/intc/arm_gicv3_cpuif.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/hw/intc/arm_gicv3_cpuif.c b/hw/intc/arm_gicv3_cpuif.c
> index 4b4cf09157..165f7e9c2f 100644
> --- a/hw/intc/arm_gicv3_cpuif.c
> +++ b/hw/intc/arm_gicv3_cpuif.c
> @@ -1797,6 +1797,9 @@ static void icc_bpr_write(CPUARMState *env, const ARMCPRegInfo *ri,
> trace_gicv3_icc_bpr_write(ri->crm == 8 ? 0 : 1,
> gicv3_redist_affid(cs), value);
>
> + /* clamp the value to 2:0, the rest os RES0 */
> + value = deposit64(0, 0, 3, value);
Surely extract, not deposit.
r~
> +
> if (grp == GICV3_G1 && gicv3_use_ns_bank(env)) {
> grp = GICV3_G1NS;
> }
> @@ -1820,7 +1823,7 @@ static void icc_bpr_write(CPUARMState *env, const ARMCPRegInfo *ri,
> value = minval;
> }
>
> - cs->icc_bpr[grp] = value & 7;
> + cs->icc_bpr[grp] = value;
> gicv3_cpuif_update(cs);
> }
>
next prev parent reply other threads:[~2025-06-18 2:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 20:10 [RFC PATCH] target/arm: clamp value to account for RES0 fields Alex Bennée
2025-06-18 2:13 ` Richard Henderson [this message]
2025-06-20 9:58 ` Peter Maydell
2025-06-20 10:16 ` Alex Bennée
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=c0bbe37c-f926-4425-9cc8-7719035bc06a@linaro.org \
--to=richard.henderson@linaro.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).