From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>,
qemu-arm@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH 2/5] target/arm: Enable FEAT_CSV2_3 for -cpu max
Date: Thu, 18 Apr 2024 18:11:44 +0200 [thread overview]
Message-ID: <0609dc37-a7d4-45f5-96d8-4122e40ac0d4@linaro.org> (raw)
In-Reply-To: <20240418152004.2106516-3-peter.maydell@linaro.org>
On 18/4/24 17:20, Peter Maydell wrote:
> FEAT_CSV2_3 adds a mechanism to identify if hardware cannot disclose
> information about whether branch targets and branch history trained
> in one hardware described context can control speculative execution
> in a different hardware context.
>
> There is no branch prediction in TCG, so we don't need to do anything
> to be compliant with this. Upadte the '-cpu max' ID registers to
> advertise the feature.
>
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> ---
> docs/system/arm/emulation.rst | 1 +
> target/arm/tcg/cpu64.c | 4 ++--
> 2 files changed, 3 insertions(+), 2 deletions(-)
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
next prev parent reply other threads:[~2024-04-18 16:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-18 15:19 [PATCH 0/5] target/arm: Update emulation.rst, add some easy features Peter Maydell
2024-04-18 15:20 ` [PATCH 1/5] docs/system/arm/emulation.rst: Add missing implemented features Peter Maydell
2024-04-19 17:37 ` Peter Maydell
2024-04-18 15:20 ` [PATCH 2/5] target/arm: Enable FEAT_CSV2_3 for -cpu max Peter Maydell
2024-04-18 16:11 ` Philippe Mathieu-Daudé [this message]
2024-04-18 15:20 ` [PATCH 3/5] target/arm: Enable FEAT_ETS2 " Peter Maydell
2024-04-18 15:20 ` [PATCH 4/5] target/arm: Implement ID_AA64MMFR3_EL1 Peter Maydell
2024-04-18 15:20 ` [PATCH 5/5] target/arm: Enable FEAT_Spec_FPACC for -cpu max Peter Maydell
2024-04-18 16:15 ` Philippe Mathieu-Daudé
2024-04-24 23:15 ` [PATCH 0/5] target/arm: Update emulation.rst, add some easy features Richard Henderson
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=0609dc37-a7d4-45f5-96d8-4122e40ac0d4@linaro.org \
--to=philmd@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).