From: Max Chou <max.chou@sifive.com>
To: Daniel Henrique Barboza <dbarboza@ventanamicro.com>
Cc: qemu-devel@nongnu.org, qemu-riscv@nongnu.org,
Palmer Dabbelt <palmer@dabbelt.com>,
Alistair Francis <alistair.francis@wdc.com>,
Weiwei Li <liwei1518@gmail.com>,
Liu Zhiwei <zhiwei_liu@linux.alibaba.com>
Subject: Re: [PATCH v2 5/9] target/riscv: Use the tb->cs_bqse as the extend tb flags.
Date: Fri, 16 Jan 2026 09:59:57 +0800 [thread overview]
Message-ID: <aWma0vO3uxd7mek9@sifive.com> (raw)
In-Reply-To: <ade8a525-c12c-4de8-9d24-9851181e04fb@ventanamicro.com>
On 2026-01-12 15:28, Daniel Henrique Barboza wrote:
> Note: typo in commit title: 'cs->bqse'
>
> On 1/8/2026 10:26 AM, Max Chou wrote:
> > We have more than 32-bits worth of state per TB, so use the
> > tb->cs_base, which is otherwise unused for RISC-V, as the extend flag.
> >
> > Signed-off-by: Max Chou <max.chou@sifive.com>
> > ---
>
> That's a neat idea. I'll use it in my e-trace series in case this series
> is merged first.
>
>
> Reviewed-by: Daniel Henrique Barboza <daniel.barboza@oss.qualcomm.com>
>
Thanks for the review, Daniel. I just discovered a typo in the patch
message, so I’ll send out the v3 to fix it.
Thanks,
rnax
next prev parent reply other threads:[~2026-01-16 2:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 13:26 [PATCH v2 0/9] Add Zvfbfa extension support Max Chou
2026-01-08 13:26 ` [PATCH v2 1/9] target/riscv: Add cfg properities for Zvfbfa extensions Max Chou
2026-01-08 13:26 ` [PATCH v2 2/9] target/riscv: Add the Zvfbfa extension implied rule Max Chou
2026-01-08 13:26 ` [PATCH v2 3/9] target/riscv: rvv: Add new VTYPE CSR field - altfmt Max Chou
2026-01-08 13:26 ` [PATCH v2 4/9] target/riscv: rvv: Introduce reset_ill_vtype to reset illegal vtype CSR Max Chou
2026-01-12 18:27 ` Daniel Henrique Barboza
2026-01-08 13:26 ` [PATCH v2 5/9] target/riscv: Use the tb->cs_bqse as the extend tb flags Max Chou
2026-01-12 18:28 ` Daniel Henrique Barboza
2026-01-16 1:59 ` Max Chou [this message]
2026-01-08 13:26 ` [PATCH v2 6/9] target/riscv: Introduce altfmt into DisasContext Max Chou
2026-01-12 18:29 ` Daniel Henrique Barboza
2026-01-08 13:26 ` [PATCH v2 7/9] target/riscv: Introduce BF16 canonical NaN for Zvfbfa extension Max Chou
2026-01-08 13:26 ` [PATCH v2 8/9] target/riscv: rvv: Support Zvfbfa vector bf16 operations Max Chou
2026-01-08 13:26 ` [PATCH v2 9/9] target/riscv: Expose Zvfbfa extension as an experimental cpu property Max Chou
2026-01-12 18:30 ` Daniel Henrique Barboza
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=aWma0vO3uxd7mek9@sifive.com \
--to=max.chou@sifive.com \
--cc=alistair.francis@wdc.com \
--cc=dbarboza@ventanamicro.com \
--cc=liwei1518@gmail.com \
--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 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.