From: Gustavo Romero <gustavo.romero@linaro.org>
To: Richard Henderson <richard.henderson@linaro.org>,
qemu-devel@nongnu.org, alex.bennee@linaro.org
Cc: philmd@linaro.org, peter.maydell@linaro.org
Subject: Re: [PATCH 1/2] target/arm: Move initialization of debug ID registers
Date: Fri, 21 Jun 2024 11:41:42 -0300 [thread overview]
Message-ID: <c9cb3219-b55a-e05a-7253-3ff270bb58fc@linaro.org> (raw)
In-Reply-To: <2af6449a-f4c2-422c-a92b-cfb11a5ae2d5@linaro.org>
Hi Richard,
On 6/20/24 3:21 PM, Richard Henderson wrote:
> On 6/20/24 11:13, Gustavo Romero wrote:
>> @@ -1268,7 +1268,10 @@ void aarch64_max_tcg_initfn(Object *obj)
>> t = FIELD_DP64(t, ID_AA64SMFR0, FA64, 1); /* FEAT_SME_FA64 */
>> cpu->isar.id_aa64smfr0 = t;
>> - /* Replicate the same data to the 32-bit id registers. */
>> + /*
>> + * Replicate the same values from the 32-bit max CPU to the 32-bit ID
>> + * registers.
>> + */
>> aa32_max_features(cpu);
>
> I think the previous comment is more accurate.
>
> There is no separate "32-bit max CPU". There is one "max CPU", which supports both 32-bit and 64-bit modes, and thus has both 32-bit and 64-bit ID registers.
I see. In v2 I reverted to the previous comment. Thanks a lot for the review.
Cheers,
Gustavo
> The rest of the patch looks good.
>
>
> r~
next prev parent reply other threads:[~2024-06-21 14:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 18:13 [PATCH 0/2] target/arm: Enable FEAT_Debugv8p8 for -cpu max Gustavo Romero
2024-06-20 18:13 ` [PATCH 1/2] target/arm: Move initialization of debug ID registers Gustavo Romero
2024-06-20 18:21 ` Richard Henderson
2024-06-21 14:41 ` Gustavo Romero [this message]
2024-06-20 18:13 ` [PATCH 2/2] target/arm: Enable FEAT_Debugv8p8 for -cpu max Gustavo Romero
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=c9cb3219-b55a-e05a-7253-3ff270bb58fc@linaro.org \
--to=gustavo.romero@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).