From: LIU Zhiwei <zhiwei_liu@linux.alibaba.com>
To: qemu-devel@nongnu.org, qemu-riscv@nongnu.org
Cc: Alistair.Francis@wdc.com, palmer@dabbelt.com,
bin.meng@windriver.com, LIU Zhiwei <zhiwei_liu@linux.alibaba.com>
Subject: [RFC PATCH 0/4] Support multiple deocde path for RISC-V
Date: Wed, 24 Aug 2022 21:03:27 +0800 [thread overview]
Message-ID: <20220824130331.21315-1-zhiwei_liu@linux.alibaba.com> (raw)
The patch set add support for disassembling XVentanaCondOps instructions.
And we can also extend it to disassemble the other custom extensions.
The target_info field in struct disassemble_info is intended to be used
by targets in any way they deem suitable. We encode the custom extension
in this field and decode the custom instructions according to this information.
LIU Zhiwei (4):
target/riscv: Use xl instead of mxl for disassemble
disas/riscv: Move down the struct rv_decode
disas/riscv: Add used_opcode_data field
target/riscv: Support Ventana disassemble
disas/riscv.c | 103 +++++++++++++++++++++++++++++++++---------
target/riscv/cpu.c | 22 ++++++++-
target/riscv/custom.h | 25 ++++++++++
3 files changed, 127 insertions(+), 23 deletions(-)
create mode 100644 target/riscv/custom.h
--
2.25.1
next reply other threads:[~2022-08-24 15:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-24 13:03 LIU Zhiwei [this message]
2022-08-24 13:03 ` [RFC PATCH 1/4] target/riscv: Use xl instead of mxl for disassemble LIU Zhiwei
2022-08-24 16:30 ` Richard Henderson
2022-08-29 10:08 ` Alistair Francis
2022-08-24 13:03 ` [RFC PATCH 2/4] disas/riscv: Move down the struct rv_decode LIU Zhiwei
2022-08-24 13:03 ` [RFC PATCH 3/4] disas/riscv: Add used_opcode_data field LIU Zhiwei
2022-08-24 13:03 ` [RFC PATCH 4/4] target/riscv: Support Ventana disassemble LIU Zhiwei
2022-08-30 9:03 ` Alistair Francis
2022-08-30 12:54 ` LIU Zhiwei
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=20220824130331.21315-1-zhiwei_liu@linux.alibaba.com \
--to=zhiwei_liu@linux.alibaba.com \
--cc=Alistair.Francis@wdc.com \
--cc=bin.meng@windriver.com \
--cc=palmer@dabbelt.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).