From: Jason Chien <jason.chien@sifive.com>
To: Daniel Henrique Barboza <dbarboza@ventanamicro.com>
Cc: qemu-devel@nongnu.org, qemu-riscv@nongnu.org,
Frank Chang <frank.chang@sifive.com>,
Max Chou <max.chou@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Alistair Francis <alistair.francis@wdc.com>,
Bin Meng <bin.meng@windriver.com>,
Weiwei Li <liwei1518@gmail.com>,
Liu Zhiwei <zhiwei_liu@linux.alibaba.com>,
Richard Henderson <richard.henderson@linaro.org>,
Andrew Jones <ajones@ventanamicro.com>
Subject: Re: [PATCH 1/5] target/riscv: Add support for Zve32x extension
Date: Thu, 21 Mar 2024 15:06:14 +0800 [thread overview]
Message-ID: <CADr__8rWGB9KZ1jn5HstvJoxtHn+1aEzLev08RAMBcbtjDYhzg@mail.gmail.com> (raw)
In-Reply-To: <16f08a8d-ba5b-430a-9276-2bf2f1b0d24d@ventanamicro.com>
[-- Attachment #1: Type: text/plain, Size: 6661 bytes --]
I will re-send shortly. Thanks.
Daniel Henrique Barboza <dbarboza@ventanamicro.com> 於 2024年3月20日 週三
上午5:19寫道:
> Hi Jason,
>
> Care to re-send please? The patches don't apply to neither
> riscv-to-apply.next
> nor master.
>
>
> Thanks,
>
> Daniel
>
> On 3/19/24 13:23, Jason Chien wrote:
> > Ping. Can anyone review the patches please?
> >
> > Jason Chien <jason.chien@sifive.com <mailto:jason.chien@sifive.com>> 於
> 2024年3月7日 週四 上午1:09寫道:
> >
> > Add support for Zve32x extension and replace some checks for Zve32f
> with
> > Zve32x, since Zve32f depends on Zve32x.
> >
> > Signed-off-by: Jason Chien <jason.chien@sifive.com <mailto:
> jason.chien@sifive.com>>
> > Reviewed-by: Frank Chang <frank.chang@sifive.com <mailto:
> frank.chang@sifive.com>>
> > Reviewed-by: Max Chou <max.chou@sifive.com <mailto:
> max.chou@sifive.com>>
> > ---
> > target/riscv/cpu.c | 1 +
> > target/riscv/cpu_cfg.h | 1 +
> > target/riscv/cpu_helper.c | 2 +-
> > target/riscv/csr.c | 2 +-
> > target/riscv/insn_trans/trans_rvv.c.inc | 4 ++--
> > target/riscv/tcg/tcg-cpu.c | 16 ++++++++--------
> > 6 files changed, 14 insertions(+), 12 deletions(-)
> >
> > diff --git a/target/riscv/cpu.c b/target/riscv/cpu.c
> > index fd0c7efdda..10ccae3323 100644
> > --- a/target/riscv/cpu.c
> > +++ b/target/riscv/cpu.c
> > @@ -152,6 +152,7 @@ const RISCVIsaExtData isa_edata_arr[] = {
> > ISA_EXT_DATA_ENTRY(zvbb, PRIV_VERSION_1_12_0, ext_zvbb),
> > ISA_EXT_DATA_ENTRY(zvbc, PRIV_VERSION_1_12_0, ext_zvbc),
> > ISA_EXT_DATA_ENTRY(zve32f, PRIV_VERSION_1_10_0, ext_zve32f),
> > + ISA_EXT_DATA_ENTRY(zve32x, PRIV_VERSION_1_10_0, ext_zve32x),
> > ISA_EXT_DATA_ENTRY(zve64f, PRIV_VERSION_1_10_0, ext_zve64f),
> > ISA_EXT_DATA_ENTRY(zve64d, PRIV_VERSION_1_10_0, ext_zve64d),
> > ISA_EXT_DATA_ENTRY(zvfbfmin, PRIV_VERSION_1_12_0,
> ext_zvfbfmin),
> > diff --git a/target/riscv/cpu_cfg.h b/target/riscv/cpu_cfg.h
> > index be39870691..beb3d10213 100644
> > --- a/target/riscv/cpu_cfg.h
> > +++ b/target/riscv/cpu_cfg.h
> > @@ -90,6 +90,7 @@ struct RISCVCPUConfig {
> > bool ext_zhinx;
> > bool ext_zhinxmin;
> > bool ext_zve32f;
> > + bool ext_zve32x;
> > bool ext_zve64f;
> > bool ext_zve64d;
> > bool ext_zvbb;
> > diff --git a/target/riscv/cpu_helper.c b/target/riscv/cpu_helper.c
> > index c994a72634..ebbe56d9a2 100644
> > --- a/target/riscv/cpu_helper.c
> > +++ b/target/riscv/cpu_helper.c
> > @@ -72,7 +72,7 @@ void cpu_get_tb_cpu_state(CPURISCVState *env,
> vaddr *pc,
> > *pc = env->xl == MXL_RV32 ? env->pc & UINT32_MAX : env->pc;
> > *cs_base = 0;
> >
> > - if (cpu->cfg.ext_zve32f) {
> > + if (cpu->cfg.ext_zve32x) {
> > /*
> > * If env->vl equals to VLMAX, we can use generic vector
> operation
> > * expanders (GVEC) to accerlate the vector operations.
> > diff --git a/target/riscv/csr.c b/target/riscv/csr.c
> > index 726096444f..d96feea5d3 100644
> > --- a/target/riscv/csr.c
> > +++ b/target/riscv/csr.c
> > @@ -93,7 +93,7 @@ static RISCVException fs(CPURISCVState *env, int
> csrno)
> >
> > static RISCVException vs(CPURISCVState *env, int csrno)
> > {
> > - if (riscv_cpu_cfg(env)->ext_zve32f) {
> > + if (riscv_cpu_cfg(env)->ext_zve32x) {
> > #if !defined(CONFIG_USER_ONLY)
> > if (!env->debugger && !riscv_cpu_vector_enabled(env)) {
> > return RISCV_EXCP_ILLEGAL_INST;
> > diff --git a/target/riscv/insn_trans/trans_rvv.c.inc
> b/target/riscv/insn_trans/trans_rvv.c.inc
> > index 9e101ab434..f00f1ee886 100644
> > --- a/target/riscv/insn_trans/trans_rvv.c.inc
> > +++ b/target/riscv/insn_trans/trans_rvv.c.inc
> > @@ -149,7 +149,7 @@ static bool do_vsetvl(DisasContext *s, int rd,
> int rs1, TCGv s2)
> > {
> > TCGv s1, dst;
> >
> > - if (!require_rvv(s) || !s->cfg_ptr->ext_zve32f) {
> > + if (!require_rvv(s) || !s->cfg_ptr->ext_zve32x) {
> > return false;
> > }
> >
> > @@ -179,7 +179,7 @@ static bool do_vsetivli(DisasContext *s, int rd,
> TCGv s1, TCGv s2)
> > {
> > TCGv dst;
> >
> > - if (!require_rvv(s) || !s->cfg_ptr->ext_zve32f) {
> > + if (!require_rvv(s) || !s->cfg_ptr->ext_zve32x) {
> > return false;
> > }
> >
> > diff --git a/target/riscv/tcg/tcg-cpu.c b/target/riscv/tcg/tcg-cpu.c
> > index ab6db817db..ce539528e6 100644
> > --- a/target/riscv/tcg/tcg-cpu.c
> > +++ b/target/riscv/tcg/tcg-cpu.c
> > @@ -501,9 +501,13 @@ void riscv_cpu_validate_set_extensions(RISCVCPU
> *cpu, Error **errp)
> > return;
> > }
> >
> > - if (cpu->cfg.ext_zve32f && !riscv_has_ext(env, RVF)) {
> > - error_setg(errp, "Zve32f/Zve64f extensions require F
> extension");
> > - return;
> > + /* The Zve32f extension depends on the Zve32x extension */
> > + if (cpu->cfg.ext_zve32f) {
> > + if (!riscv_has_ext(env, RVF)) {
> > + error_setg(errp, "Zve32f/Zve64f extensions require F
> extension");
> > + return;
> > + }
> > + cpu_cfg_ext_auto_update(cpu, CPU_CFG_OFFSET(ext_zve32x),
> true);
> > }
> >
> > if (cpu->cfg.ext_zvfh) {
> > @@ -653,13 +657,9 @@ void riscv_cpu_validate_set_extensions(RISCVCPU
> *cpu, Error **errp)
> > cpu_cfg_ext_auto_update(cpu, CPU_CFG_OFFSET(ext_zvbc),
> true);
> > }
> >
> > - /*
> > - * In principle Zve*x would also suffice here, were they
> supported
> > - * in qemu
> > - */
> > if ((cpu->cfg.ext_zvbb || cpu->cfg.ext_zvkb ||
> cpu->cfg.ext_zvkg ||
> > cpu->cfg.ext_zvkned || cpu->cfg.ext_zvknha ||
> cpu->cfg.ext_zvksed ||
> > - cpu->cfg.ext_zvksh) && !cpu->cfg.ext_zve32f) {
> > + cpu->cfg.ext_zvksh) && !cpu->cfg.ext_zve32x) {
> > error_setg(errp,
> > "Vector crypto extensions require V or Zve*
> extensions");
> > return;
> > --
> > 2.43.2
> >
>
[-- Attachment #2: Type: text/html, Size: 8866 bytes --]
next prev parent reply other threads:[~2024-03-21 7:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 17:08 [PATCH 0/5] target/riscv: Support Zve32x and Zve64x extensions Jason Chien
2024-03-06 17:08 ` [PATCH 1/5] target/riscv: Add support for Zve32x extension Jason Chien
2024-03-19 16:23 ` Jason Chien
2024-03-19 21:19 ` Daniel Henrique Barboza
2024-03-21 7:06 ` Jason Chien [this message]
2024-03-06 17:08 ` [PATCH 2/5] target/riscv: Expose Zve32x extension to users Jason Chien
2024-03-06 17:08 ` [PATCH 3/5] target/riscv: Add support for Zve64x extension Jason Chien
2024-03-06 17:08 ` [PATCH 4/5] target/riscv: Expose Zve64x extension to users Jason Chien
2024-03-21 12:20 ` Daniel Henrique Barboza
2024-03-06 17:08 ` [PATCH 5/5] target/riscv: Relax vector register check in RISCV gdbstub Jason Chien
2024-03-19 16:23 ` [PATCH 0/5] target/riscv: Support Zve32x and Zve64x extensions Jason Chien
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=CADr__8rWGB9KZ1jn5HstvJoxtHn+1aEzLev08RAMBcbtjDYhzg@mail.gmail.com \
--to=jason.chien@sifive.com \
--cc=ajones@ventanamicro.com \
--cc=alistair.francis@wdc.com \
--cc=bin.meng@windriver.com \
--cc=dbarboza@ventanamicro.com \
--cc=frank.chang@sifive.com \
--cc=liwei1518@gmail.com \
--cc=max.chou@sifive.com \
--cc=palmer@dabbelt.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=richard.henderson@linaro.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).