From: Peter Maydell <peter.maydell@linaro.org>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-devel@nongnu.org,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
qemu-stable@nongnu.org,
"open list:ARM TCG CPUs" <qemu-arm@nongnu.org>
Subject: Re: [PATCH v2] target/arm: properly document FEAT_CRC32
Date: Tue, 29 Aug 2023 14:23:49 +0100 [thread overview]
Message-ID: <CAFEAcA-n7KVVLEUjYYkPMbLPVn+daXb4iDwe2H3x7KF+BeKt+w@mail.gmail.com> (raw)
In-Reply-To: <20230824075406.1515566-1-alex.bennee@linaro.org>
On Thu, 24 Aug 2023 at 08:54, Alex Bennée <alex.bennee@linaro.org> wrote:
>
> This is a mandatory feature for Armv8.1 architectures but we don't
> state the feature clearly in our emulation list. Also include
> FEAT_CRC32 comment in aarch64_max_tcg_initfn for ease of grepping.
>
> Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> Cc: qemu-stable@nongnu.org
> Message-Id: <20230222110104.3996971-1-alex.bennee@linaro.org>
>
> ---
> v2
> - dropped the breakdown of setting ID registers in other CPU init fns
> ---
> docs/system/arm/emulation.rst | 1 +
> target/arm/tcg/cpu64.c | 2 +-
> 2 files changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/docs/system/arm/emulation.rst b/docs/system/arm/emulation.rst
> index bdafc68819..65d1f39f4b 100644
> --- a/docs/system/arm/emulation.rst
> +++ b/docs/system/arm/emulation.rst
> @@ -14,6 +14,7 @@ the following architecture extensions:
> - FEAT_BBM at level 2 (Translation table break-before-make levels)
> - FEAT_BF16 (AArch64 BFloat16 instructions)
> - FEAT_BTI (Branch Target Identification)
> +- FEAT_CRC32 (CRC32 instruction)
Applied to target-arm.next, thanks. I pluralized "instructions"
here to match the Arm ARM text.
-- PMM
prev parent reply other threads:[~2023-08-29 13:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 7:54 [PATCH v2] target/arm: properly document FEAT_CRC32 Alex Bennée
2023-08-29 13:23 ` Peter Maydell [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=CAFEAcA-n7KVVLEUjYYkPMbLPVn+daXb4iDwe2H3x7KF+BeKt+w@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).