From: Peter Maydell <peter.maydell@linaro.org>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: yuzenghui@huawei.com, qemu-devel@nongnu.org
Subject: Re: [PATCH 1/4] target/arm: Fix sve_zcr_len_for_el for VHE mode running
Date: Fri, 28 Jan 2022 18:18:48 +0000 [thread overview]
Message-ID: <CAFEAcA-SRk=Bf9n2pcEtKg6m89e8Q6nmFrya1hOK5e7BDng-1A@mail.gmail.com> (raw)
In-Reply-To: <20220127063428.30212-2-richard.henderson@linaro.org>
On Thu, 27 Jan 2022 at 06:34, Richard Henderson
<richard.henderson@linaro.org> wrote:
>
> When HCR_EL2.{E2H,TGE} == '11', ZCR_EL1 is unused.
>
> Reported-by: Zenghui Yu <yuzenghui@huawei.com>
> Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
> ---
> target/arm/helper.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
thanks
-- PMM
next prev parent reply other threads:[~2022-01-28 18:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 6:34 [PATCH 0/4] target/arm: SVE fixes versus VHE Richard Henderson
2022-01-27 6:34 ` [PATCH 1/4] target/arm: Fix sve_zcr_len_for_el for VHE mode running Richard Henderson
2022-01-28 18:18 ` Peter Maydell [this message]
2022-01-29 6:49 ` Zenghui Yu via
2022-01-27 6:34 ` [PATCH 2/4] target/arm: Tidy sve_exception_el for CPACR_EL1 access Richard Henderson
2022-01-28 18:15 ` Peter Maydell
2022-01-29 6:50 ` Zenghui Yu via
2022-01-27 6:34 ` [PATCH 3/4] target/arm: Fix {fp, sve}_exception_el for VHE mode running Richard Henderson
2022-01-28 18:23 ` Peter Maydell
2022-01-29 6:50 ` [PATCH 3/4] target/arm: Fix {fp,sve}_exception_el " Zenghui Yu via
2022-01-27 6:34 ` [PATCH 4/4] target/arm: Use CPTR_TFP with CPTR_EL3 in fp_exception_el Richard Henderson
2022-01-28 18:13 ` Peter Maydell
2022-01-29 6:55 ` Zenghui Yu via
2022-02-03 11:31 ` [PATCH 0/4] target/arm: SVE fixes versus VHE Peter Maydell
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-SRk=Bf9n2pcEtKg6m89e8Q6nmFrya1hOK5e7BDng-1A@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=yuzenghui@huawei.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.