From: Max Chou <max.chou@sifive.com>
To: qemu-devel@nongnu.org, qemu-riscv@nongnu.org
Cc: Max Chou <max.chou@sifive.com>
Subject: [PATCH 00/14] Update RISC-V vector crypto to ratified v1.0.0
Date: Wed, 25 Oct 2023 23:13:24 +0800 [thread overview]
Message-ID: <20231025151341.725477-1-max.chou@sifive.com> (raw)
This patchset updates the RISC-V vector cryptography support to the
ratified version v1.0.0 (commit 1769c26, released on 2023/10) with
following items:
- Add Zvkb, Zvkt, and other shorthand extensions(Zvkn, Zvknc, Zvkng,
Zvks, Zvksc, Zvksg).
- Supports the disassembler for vector crypto extensions.
- Move vector crypto extensions from experimental extensions to ratified
extensions.
- Replace TAB indentations with spaces in disas/riscv.c.
https://github.com/riscv/riscv-crypto/releases/tag/v1.0.0
Max Chou (14):
target/riscv: Add cfg property for Zvkt extension
target/riscv: Expose Zvkt extension property
target/riscv: Add cfg property for Zvkb extension
target/riscv: Replace Zvbb checking by Zvkb
target/riscv: Expose Zvkb extension property
target/riscv: Add cfg properties for Zvkn[c|g] extensions
target/riscv: Expose Zvkn[c|g] extnesion properties
target/riscv: Add cfg properties for Zvks[c|g] extensions
target/riscv: Expose Zvks[c|g] extnesion properties
target/riscv: Move vector crypto extensions to riscv_cpu_extensions
disas/riscv: Add rv_fmt_vd_vs2_uimm format
disas/riscv: Add rv_codec_vror_vi for vror.vi
disas/riscv: Add support for vector crypto extensions
disas/riscv: Replace TABs with space
disas/riscv.c | 154 ++++++++++++++++++++++-
disas/riscv.h | 2 +
target/riscv/cpu.c | 36 ++++--
target/riscv/cpu_cfg.h | 8 ++
target/riscv/insn_trans/trans_rvvk.c.inc | 37 ++++--
target/riscv/tcg/tcg-cpu.c | 48 ++++++-
6 files changed, 256 insertions(+), 29 deletions(-)
--
2.34.1
next reply other threads:[~2023-10-25 15:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 15:13 Max Chou [this message]
2023-10-25 15:13 ` [PATCH 01/14] target/riscv: Add cfg property for Zvkt extension Max Chou
2023-10-30 4:47 ` Alistair Francis
2023-10-25 15:13 ` [PATCH 02/14] target/riscv: Expose Zvkt extension property Max Chou
2023-10-25 15:13 ` [PATCH 03/14] target/riscv: Add cfg property for Zvkb extension Max Chou
2023-10-25 15:13 ` [PATCH 04/14] target/riscv: Replace Zvbb checking by Zvkb Max Chou
2023-10-25 15:13 ` [PATCH 05/14] target/riscv: Expose Zvkb extension property Max Chou
2023-10-25 15:13 ` [PATCH 06/14] target/riscv: Add cfg properties for Zvkn[c|g] extensions Max Chou
2023-10-25 15:13 ` [PATCH 07/14] target/riscv: Expose Zvkn[c|g] extnesion properties Max Chou
2023-10-25 15:13 ` [PATCH 08/14] target/riscv: Add cfg properties for Zvks[c|g] extensions Max Chou
2023-10-25 15:13 ` [PATCH 09/14] target/riscv: Expose Zvks[c|g] extnesion properties Max Chou
2023-10-25 15:13 ` [PATCH 10/14] target/riscv: Move vector crypto extensions to riscv_cpu_extensions Max Chou
2023-10-25 15:13 ` [PATCH 11/14] disas/riscv: Add rv_fmt_vd_vs2_uimm format Max Chou
2023-10-25 15:13 ` [PATCH 12/14] disas/riscv: Add rv_codec_vror_vi for vror.vi Max Chou
2023-10-25 15:13 ` [PATCH 13/14] disas/riscv: Add support for vector crypto extensions Max Chou
2023-10-25 15:13 ` [PATCH 14/14] disas/riscv: Replace TABs with space Max Chou
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=20231025151341.725477-1-max.chou@sifive.com \
--to=max.chou@sifive.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
/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).