From: Richard Henderson <richard.henderson@linaro.org>
To: liweiwei <liweiwei@iscas.ac.cn>,
palmer@dabbelt.com, alistair.francis@wdc.com,
bin.meng@windriver.com, qemu-riscv@nongnu.org,
qemu-devel@nongnu.org
Cc: wangjunqiang@iscas.ac.cn, lazyparser@gmail.com,
luruibo2000@163.com, lustrew@foxmail.com
Subject: Re: [RFC 1/6] target/riscv: rvk: add flag support for Zbk[bcx]
Date: Tue, 2 Nov 2021 10:18:38 -0400 [thread overview]
Message-ID: <97624133-30f2-fdc4-4f3c-0cc843f0768c@linaro.org> (raw)
In-Reply-To: <20211102031128.17296-2-liweiwei@iscas.ac.cn>
On 11/1/21 11:11 PM, liweiwei wrote:
> +++ b/target/riscv/cpu.c
> @@ -472,15 +472,15 @@ static void riscv_cpu_realize(DeviceState *dev, Error **errp)
> error_setg(errp,
> "I and E extensions are incompatible");
> return;
> - }
> + }
>
> if (!cpu->cfg.ext_i && !cpu->cfg.ext_e) {
> error_setg(errp,
> "Either I or E extension must be set");
> return;
> - }
> + }
>
> - if (cpu->cfg.ext_g && !(cpu->cfg.ext_i & cpu->cfg.ext_m &
> + if (cpu->cfg.ext_g && !(cpu->cfg.ext_i & cpu->cfg.ext_m &
> cpu->cfg.ext_a & cpu->cfg.ext_f &
> cpu->cfg.ext_d)) {
> warn_report("Setting G will also set IMAFD");
This re-indentation should not be happening.
> + DEFINE_PROP_BOOL("x-zbkb", RISCVCPU, cfg.ext_zbkb, false),
> + DEFINE_PROP_BOOL("x-zbkc", RISCVCPU, cfg.ext_zbkc, false),
> + DEFINE_PROP_BOOL("x-zbkx", RISCVCPU, cfg.ext_zbkx, false),
The properties cannot be exposed until the end.
> bool ext_zbb;
> bool ext_zbc;
> bool ext_zbs;
> + bool ext_zbkb;
> + bool ext_zbkc;
> + bool ext_zbkx;
Better to keep them alphabetical: zbk* < zbs.
r~
next prev parent reply other threads:[~2021-11-02 14:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 3:11 [RFC 0/6] support subsets of scalar crypto extension liweiwei
2021-11-02 3:11 ` [RFC 1/6] target/riscv: rvk: add flag support for Zbk[bcx] liweiwei
2021-11-02 14:18 ` Richard Henderson [this message]
2021-11-02 15:00 ` liweiwei
2021-11-02 3:11 ` [RFC 2/6] target/riscv: rvk: add implementation of instructions for Zbk* - reuse partial instructions of Zbb/Zbc extensions - add brev8 packh, unzip, zip, etc liweiwei
2021-11-02 15:44 ` Richard Henderson
2021-11-03 0:56 ` liweiwei
2021-11-02 3:11 ` [RFC 3/6] target/riscv: rvk: add flag support for Zk/Zkn/Zknd/Zknd/Zkne/Zknh/Zks/Zksed/Zksh/Zkr liweiwei
2021-11-02 17:56 ` Richard Henderson
2021-11-03 1:06 ` liweiwei
2021-11-03 1:21 ` Richard Henderson
2021-11-03 7:22 ` liweiwei
2021-11-02 3:11 ` [RFC 4/6] target/riscv: rvk: add implementation of instructions for Zk* liweiwei
2021-11-02 18:56 ` Richard Henderson
2021-11-03 1:08 ` liweiwei
2021-11-02 3:11 ` [RFC 5/6] target/riscv: rvk: add CSR support for Zkr: - add SEED CSR - add USEED, SSEED fields for MSECCFG CSR liweiwei
2021-11-02 3:11 ` [RFC 6/6] disas/riscv.c: rvk: add disas support for Zbk* and Zk* instructions liweiwei
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=97624133-30f2-fdc4-4f3c-0cc843f0768c@linaro.org \
--to=richard.henderson@linaro.org \
--cc=alistair.francis@wdc.com \
--cc=bin.meng@windriver.com \
--cc=lazyparser@gmail.com \
--cc=liweiwei@iscas.ac.cn \
--cc=luruibo2000@163.com \
--cc=lustrew@foxmail.com \
--cc=palmer@dabbelt.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=wangjunqiang@iscas.ac.cn \
/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).