From: Chao Liu <lc00631@tecorigin.com>
To: alistair23@gmail.com
Cc: alistair.francis@wdc.com, bmeng.cn@gmail.com,
dbarboza@ventanamicro.com, lc00631@tecorigin.com,
liwei1518@gmail.com, palmer@dabbelt.com, qemu-devel@nongnu.org,
qemu-riscv@nongnu.org, zhiwei_liu@linux.alibaba.com,
zqz00548@tecorigin.com
Subject: [PATCH v4 0/2] Enhanced VSTART and VL checks for vector instructions
Date: Mon, 10 Mar 2025 10:35:23 +0800 [thread overview]
Message-ID: <cover.1741573286.git.lc00631@tecorigin.com> (raw)
Hi, Alistair:
I rebase both patches based on the riscv-to-apply.next branch and tested them.
https://github.com/alistair23/qemu/tree/riscv-to-apply.next
Only the first patch had two conflicts, which were resolved nicely,
and the second patch rebased fine, so you can review it again if necessary,
thanks!
PATCH v3 review:
https://lore.kernel.org/qemu-riscv/71f15782-ec28-4763-8197-c10ec12811ec@ventanamicro.com/
PATCH v2 review:
https://lore.kernel.org/qemu-devel/61e8f7d8-607a-4d63-b9dd-cfbfc840716e@ventanamicro.com/
PATCH v1 review:
https://lore.kernel.org/qemu-devel/CAKmqyKPFYxhK8PANOVzV3FMWxd79wZSJYLWkKOAgEMt_b2KvZA@mail.gmail.com/
--
Regards,
Chao
Chao Liu (2):
target/riscv: refactor VSTART_CHECK_EARLY_EXIT() to accept vl as a
parameter
target/riscv: fix handling of nop for vstart >= vl in some vector
instruction
target/riscv/vcrypto_helper.c | 32 ++++++-------
target/riscv/vector_helper.c | 83 ++++++++++++++++++---------------
target/riscv/vector_internals.c | 4 +-
target/riscv/vector_internals.h | 12 ++---
4 files changed, 69 insertions(+), 62 deletions(-)
--
2.48.1
next reply other threads:[~2025-03-10 2:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-10 2:35 Chao Liu [this message]
2025-03-10 2:35 ` [PATCH v4 1/2] target/riscv: refactor VSTART_CHECK_EARLY_EXIT() to accept vl as a parameter Chao Liu
2025-03-10 2:35 ` [PATCH v4 2/2] target/riscv: fix handling of nop for vstart >= vl in some vector instruction Chao Liu
2025-03-24 4:48 ` Michael Tokarev
2025-03-24 11:18 ` Daniel Henrique Barboza
2025-03-10 22:52 ` [PATCH v4 0/2] Enhanced VSTART and VL checks for vector instructions 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=cover.1741573286.git.lc00631@tecorigin.com \
--to=lc00631@tecorigin.com \
--cc=alistair.francis@wdc.com \
--cc=alistair23@gmail.com \
--cc=bmeng.cn@gmail.com \
--cc=dbarboza@ventanamicro.com \
--cc=liwei1518@gmail.com \
--cc=palmer@dabbelt.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=zhiwei_liu@linux.alibaba.com \
--cc=zqz00548@tecorigin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.