From: Richard Henderson <richard.henderson@linaro.org>
To: Gustavo Romero <gustavo.romero@linaro.org>,
qemu-arm@nongnu.org, alex.bennee@linaro.org
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH v5 5/6] target/arm: Implement FEAT_MEC cache instructions
Date: Thu, 10 Jul 2025 10:54:14 -0600 [thread overview]
Message-ID: <f256b198-6150-48a3-a97b-5f0c2cc072ce@linaro.org> (raw)
In-Reply-To: <20250710163858.1094780-6-gustavo.romero@linaro.org>
On 7/10/25 10:38, Gustavo Romero wrote:
> This commit implements the two cache maintenance instructions introduced
> by FEAT_MEC, DC CIPAE and DC CIGDPAE.
>
> Because QEMU does not model the cache topology, all cache maintenance
> instructions are implemented as NOPs, hence these new instructions are
> implemented as NOPs too.
>
> Signed-off-by: Gustavo Romero<gustavo.romero@linaro.org>
> ---
> target/arm/helper.c | 24 ++++++++++++++++++++++++
> 1 file changed, 24 insertions(+)
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
r~
next prev parent reply other threads:[~2025-07-10 17:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 16:38 [PATCH-for-10.1 v5 0/6] target/arm: Add FEAT_MEC to max cpu Gustavo Romero
2025-07-10 16:38 ` [PATCH v5 1/6] target/arm: Add the MECEn SCR_EL3 bit Gustavo Romero
2025-07-10 16:38 ` [PATCH v5 2/6] target/arm: Add FEAT_MEC registers Gustavo Romero
2025-07-10 16:38 ` [PATCH v5 3/6] target/arm: Add FEAT_SCTLR2 Gustavo Romero
2025-07-10 16:52 ` Richard Henderson
2025-07-10 16:38 ` [PATCH v5 4/6] target/arm: Add FEAT_TCR2 Gustavo Romero
2025-07-10 16:52 ` Richard Henderson
2025-07-10 16:38 ` [PATCH v5 5/6] target/arm: Implement FEAT_MEC cache instructions Gustavo Romero
2025-07-10 16:54 ` Richard Henderson [this message]
2025-07-10 16:38 ` [PATCH v5 6/6] target/arm: Advertise FEAT_MEC in 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=f256b198-6150-48a3-a97b-5f0c2cc072ce@linaro.org \
--to=richard.henderson@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=gustavo.romero@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).