From: Daniel Henrique Barboza <dbarboza@ventanamicro.com>
To: qemu-devel@nongnu.org
Cc: qemu-riscv@nongnu.org, alistair.francis@wdc.com,
bmeng@tinylab.org, liweiwei@iscas.ac.cn,
zhiwei_liu@linux.alibaba.com, palmer@rivosinc.com,
Daniel Henrique Barboza <dbarboza@ventanamicro.com>
Subject: [PATCH v8 00/11] target/riscv: rework CPU extension validation
Date: Fri, 21 Apr 2023 10:27:16 -0300 [thread overview]
Message-ID: <20230421132727.121462-1-dbarboza@ventanamicro.com> (raw)
Hi,
This version dropped patch 12 from v7. Alistair mentioned that it would
limiti static CPUs needlesly, since there's nothing preventing a static
CPU to allow for extension changes during runtime, and that misa-w is
enough to prevent write_misa() during runtime. I agree.
I also amended the commit message of patch 11 to remove any mention
about misa_ext_mask rollbacks (which the code wasn't doing). The patch
itself is changing validate_set_extensions() to avoid misa_ext_mask to
be overwritten during write_misa() in the first place, so no
misa_ext_mask rollback should be even mentioned.
Changes from v7:
- patch 12: drooped
- patch 11: use a sane commit message.
- v7 link: https://lists.gnu.org/archive/html/qemu-devel/2023-04/msg02916.html
Daniel Henrique Barboza (9):
target/riscv/cpu.c: add riscv_cpu_validate_v()
target/riscv/cpu.c: remove set_vext_version()
target/riscv/cpu.c: remove set_priv_version()
target/riscv: add PRIV_VERSION_LATEST
target/riscv/cpu.c: add priv_spec validate/disable_exts helpers
target/riscv/cpu.c: add riscv_cpu_validate_misa_mxl()
target/riscv/cpu.c: validate extensions before riscv_timer_init()
target/riscv/cpu.c: remove cfg setup from riscv_cpu_init()
target/riscv: rework write_misa()
Weiwei Li (2):
target/riscv: Mask the implicitly enabled extensions in isa_string
based on priv version
target/riscv: Update check for Zca/Zcf/Zcd
target/riscv/cpu.c | 333 ++++++++++++++----------
target/riscv/cpu.h | 3 +
target/riscv/csr.c | 47 ++--
target/riscv/insn_trans/trans_rvd.c.inc | 12 +-
target/riscv/insn_trans/trans_rvf.c.inc | 14 +-
target/riscv/insn_trans/trans_rvi.c.inc | 5 +-
target/riscv/translate.c | 5 +-
7 files changed, 244 insertions(+), 175 deletions(-)
--
2.40.0
next reply other threads:[~2023-04-21 13:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 13:27 Daniel Henrique Barboza [this message]
2023-04-21 13:27 ` [PATCH v8 01/11] target/riscv/cpu.c: add riscv_cpu_validate_v() Daniel Henrique Barboza
2023-04-21 13:27 ` [PATCH v8 02/11] target/riscv/cpu.c: remove set_vext_version() Daniel Henrique Barboza
2023-04-21 13:27 ` [PATCH v8 03/11] target/riscv/cpu.c: remove set_priv_version() Daniel Henrique Barboza
2023-04-21 13:27 ` [PATCH v8 04/11] target/riscv: add PRIV_VERSION_LATEST Daniel Henrique Barboza
2023-04-21 13:27 ` [PATCH v8 05/11] target/riscv: Mask the implicitly enabled extensions in isa_string based on priv version Daniel Henrique Barboza
2023-04-21 13:27 ` [PATCH v8 06/11] target/riscv: Update check for Zca/Zcf/Zcd Daniel Henrique Barboza
2023-04-21 13:27 ` [PATCH v8 07/11] target/riscv/cpu.c: add priv_spec validate/disable_exts helpers Daniel Henrique Barboza
2023-04-21 13:27 ` [PATCH v8 08/11] target/riscv/cpu.c: add riscv_cpu_validate_misa_mxl() Daniel Henrique Barboza
2023-04-21 13:27 ` [PATCH v8 09/11] target/riscv/cpu.c: validate extensions before riscv_timer_init() Daniel Henrique Barboza
2023-04-21 13:27 ` [PATCH v8 10/11] target/riscv/cpu.c: remove cfg setup from riscv_cpu_init() Daniel Henrique Barboza
2023-04-21 13:27 ` [PATCH v8 11/11] target/riscv: rework write_misa() Daniel Henrique Barboza
2023-05-07 23:25 ` Alistair Francis
2023-05-08 10:28 ` Daniel Henrique Barboza
2023-05-17 4:48 ` Alistair Francis
2023-05-17 9:43 ` Daniel Henrique Barboza
2023-05-12 12:41 ` Daniel Henrique Barboza
2023-05-17 4:49 ` Alistair Francis
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=20230421132727.121462-1-dbarboza@ventanamicro.com \
--to=dbarboza@ventanamicro.com \
--cc=alistair.francis@wdc.com \
--cc=bmeng@tinylab.org \
--cc=liweiwei@iscas.ac.cn \
--cc=palmer@rivosinc.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).