From: Richard Henderson <richard.henderson@linaro.org>
To: LIU Zhiwei <zhiwei_liu@linux.alibaba.com>, qemu-devel@nongnu.org
Cc: Alistair.Francis@wdc.com, palmer@dabbelt.com,
bin.meng@windriver.com, liweiwei@iscas.ac.cn,
dbarboza@ventanamicro.com, qemu-riscv@nongnu.org
Subject: Re: [PATCH v2 4/4] target/riscv: Add a tb flags field for vstart
Date: Fri, 24 Mar 2023 10:08:10 -0700 [thread overview]
Message-ID: <b6f0dcb7-d4f0-cce1-4527-1b7720b04647@linaro.org> (raw)
In-Reply-To: <20230324143031.1093-5-zhiwei_liu@linux.alibaba.com>
On 3/24/23 07:30, LIU Zhiwei wrote:
> Once we mistook the vstart directly from the env->vstart. As env->vstart is not
> a constant, we should record it in the tb flags if we want to use
> it in translation.
>
> Reported-by: Richard Henderson<richard.henderson@linaro.org>
> Signed-off-by: LIU Zhiwei<zhiwei_liu@linux.alibaba.com>
> Reviewed-by: Weiwei Li<liweiwei@iscas.ac.cn>
> ---
> target/riscv/cpu.h | 21 +++++++++++----------
> target/riscv/cpu_helper.c | 1 +
> target/riscv/insn_trans/trans_rvv.c.inc | 14 +++++++-------
> target/riscv/translate.c | 4 ++--
> 4 files changed, 21 insertions(+), 19 deletions(-)
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
r~
prev parent reply other threads:[~2023-03-24 17:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230324143031.1093-1-zhiwei_liu@linux.alibaba.com>
[not found] ` <20230324143031.1093-2-zhiwei_liu@linux.alibaba.com>
2023-03-24 17:05 ` [PATCH v2 1/4] target/riscv: Extract virt enabled state from tb flags Richard Henderson
[not found] ` <20230324143031.1093-3-zhiwei_liu@linux.alibaba.com>
2023-03-24 17:06 ` [PATCH v2 2/4] target/riscv: Add a general status enum for extensions Richard Henderson
[not found] ` <20230324143031.1093-4-zhiwei_liu@linux.alibaba.com>
2023-03-24 17:07 ` [PATCH v2 3/4] target/riscv: Encode the FS and VS on a normal way for tb flags Richard Henderson
[not found] ` <20230324143031.1093-5-zhiwei_liu@linux.alibaba.com>
2023-03-24 17:08 ` Richard Henderson [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=b6f0dcb7-d4f0-cce1-4527-1b7720b04647@linaro.org \
--to=richard.henderson@linaro.org \
--cc=Alistair.Francis@wdc.com \
--cc=bin.meng@windriver.com \
--cc=dbarboza@ventanamicro.com \
--cc=liweiwei@iscas.ac.cn \
--cc=palmer@dabbelt.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=zhiwei_liu@linux.alibaba.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 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).