From: Richard Henderson <richard.henderson@linaro.org>
To: Pierrick Bouvier <pierrick.bouvier@linaro.org>, qemu-devel@nongnu.org
Subject: Re: [PATCH 03/12] docs/system/arm/emulation: add FEAT_SSBS2
Date: Sat, 23 Nov 2024 07:45:32 -0600 [thread overview]
Message-ID: <28fabc27-29e1-4692-870c-69c41b29b9fa@linaro.org> (raw)
In-Reply-To: <20241122225049.1617774-4-pierrick.bouvier@linaro.org>
On 11/22/24 16:50, Pierrick Bouvier wrote:
> Signed-off-by: Pierrick Bouvier <pierrick.bouvier@linaro.org>
> ---
> docs/system/arm/emulation.rst | 1 +
> 1 file changed, 1 insertion(+)
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
>
> diff --git a/docs/system/arm/emulation.rst b/docs/system/arm/emulation.rst
> index af613b9c8b8..50d0250b1eb 100644
> --- a/docs/system/arm/emulation.rst
> +++ b/docs/system/arm/emulation.rst
> @@ -137,6 +137,7 @@ the following architecture extensions:
> - FEAT_SVE2 (Scalable Vector Extension version 2)
> - FEAT_SPECRES (Speculation restriction instructions)
> - FEAT_SSBS (Speculative Store Bypass Safe)
> +- FEAT_SSBS2 (MRS and MSR instructions for SSBS version 2)
> - FEAT_TGran16K (Support for 16KB memory translation granule size at stage 1)
> - FEAT_TGran4K (Support for 4KB memory translation granule size at stage 1)
> - FEAT_TGran64K (Support for 64KB memory translation granule size at stage 1)
next prev parent reply other threads:[~2024-11-23 13:46 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-22 22:50 [PATCH 00/12] Minor fixes for Arm documentation Pierrick Bouvier
2024-11-22 22:50 ` [PATCH 01/12] docs/system/arm/emulation: mention armv9 Pierrick Bouvier
2024-11-23 13:41 ` Richard Henderson
2024-11-22 22:50 ` [PATCH 02/12] docs/system/arm/emulation: fix typo in feature name Pierrick Bouvier
2024-11-23 13:41 ` Richard Henderson
2024-11-22 22:50 ` [PATCH 03/12] docs/system/arm/emulation: add FEAT_SSBS2 Pierrick Bouvier
2024-11-23 13:45 ` Richard Henderson [this message]
2024-11-22 22:50 ` [PATCH 04/12] target/arm/tcg/: fix typo in FEAT name Pierrick Bouvier
2024-11-23 5:42 ` Philippe Mathieu-Daudé
2024-11-23 13:55 ` Richard Henderson
2024-11-22 22:50 ` [PATCH 05/12] docs/system/arm/: add FEAT_MTE_ASYNC Pierrick Bouvier
2024-11-23 13:57 ` Richard Henderson
2024-11-22 22:50 ` [PATCH 06/12] docs/system/arm/: add FEAT_DoubleLock Pierrick Bouvier
2024-11-22 22:50 ` [PATCH 07/12] docs/system/arm/fby35: update link to product page Pierrick Bouvier
2024-11-23 5:43 ` Philippe Mathieu-Daudé
2024-11-23 13:58 ` Richard Henderson
2024-11-22 22:50 ` [PATCH 08/12] docs/system/arm/orangepi: update links Pierrick Bouvier
2024-11-26 19:00 ` Pierrick Bouvier
2024-11-26 20:10 ` Niek Linnenbank
2024-11-28 20:18 ` Pierrick Bouvier
2024-11-22 22:50 ` [PATCH 09/12] docs/system/arm/fby35: document execute-in-place property Pierrick Bouvier
2024-11-22 22:50 ` [PATCH 10/12] docs/system/arm/xlnx-versal-virt: document ospi-flash property Pierrick Bouvier
2024-11-22 22:50 ` [PATCH 11/12] docs/system/arm/virt: document missing properties Pierrick Bouvier
2024-11-25 17:02 ` Peter Maydell
2024-11-26 18:46 ` Pierrick Bouvier
2024-11-22 22:50 ` [PATCH 12/12] docs/system/arm/aspeed: add missing model supermicrox11spi-bmc Pierrick Bouvier
2024-11-24 23:45 ` Andrew Jeffery
2024-11-26 16:24 ` [PATCH 00/12] Minor fixes for Arm documentation Peter Maydell
2024-11-26 18:31 ` Pierrick Bouvier
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=28fabc27-29e1-4692-870c-69c41b29b9fa@linaro.org \
--to=richard.henderson@linaro.org \
--cc=pierrick.bouvier@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).