From: Weiwei Li <liweiwei@iscas.ac.cn>
To: palmer@dabbelt.com, alistair.francis@wdc.com,
bin.meng@windriver.com, qemu-riscv@nongnu.org,
qemu-devel@nongnu.org
Cc: wangjunqiang@iscas.ac.cn, Weiwei Li <liweiwei@iscas.ac.cn>,
lazyparser@gmail.com
Subject: [PATCH v2 0/3] support subsets of virtual memory extension
Date: Fri, 31 Dec 2021 16:09:20 +0800 [thread overview]
Message-ID: <20211231080923.24252-1-liweiwei@iscas.ac.cn> (raw)
This patchset implements virtual memory related RISC-V extensions: Svnapot version 1.0, Svinval vesion 1.0, Svpbmt version 1.0.
Specification:
https://github.com/riscv/virtual-memory/tree/main/specs
The port is available here:
https://github.com/plctlab/plct-qemu/tree/plct-virtmem-upstream-v2
To test this implementation, specify cpu argument with 'x-svinval=true,x-svnapot=true,x-svpbmt=true'.
This implementation can pass the riscv-tests for rv64ssvnapot.
v2:
* add extension check for svnapot and svpbmt
Weiwei Li (3):
target/riscv: add support for svnapot extension
target/riscv: add support for svinval extension
target/riscv: add support for svpbmt extension
target/riscv/cpu.c | 3 +
target/riscv/cpu.h | 3 +
target/riscv/cpu_bits.h | 4 ++
target/riscv/cpu_helper.c | 27 ++++++--
target/riscv/insn32.decode | 7 ++
target/riscv/insn_trans/trans_svinval.c.inc | 75 +++++++++++++++++++++
target/riscv/translate.c | 1 +
7 files changed, 116 insertions(+), 4 deletions(-)
create mode 100644 target/riscv/insn_trans/trans_svinval.c.inc
--
2.17.1
next reply other threads:[~2021-12-31 8:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-31 8:09 Weiwei Li [this message]
2021-12-31 8:09 ` [PATCH v2 1/3] target/riscv: add support for svnapot extension Weiwei Li
2022-01-01 13:17 ` Anup Patel
2021-12-31 8:09 ` [PATCH v2 2/3] target/riscv: add support for svinval extension Weiwei Li
2022-01-01 13:15 ` Anup Patel
2022-01-02 5:41 ` Weiwei Li
2021-12-31 8:09 ` [PATCH v2 3/3] target/riscv: add support for svpbmt extension Weiwei Li
2022-01-01 13:19 ` Anup Patel
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=20211231080923.24252-1-liweiwei@iscas.ac.cn \
--to=liweiwei@iscas.ac.cn \
--cc=alistair.francis@wdc.com \
--cc=bin.meng@windriver.com \
--cc=lazyparser@gmail.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).