From: Alistair Francis <alistair23@gmail.com>
To: Jason Chien <jason.chien@sifive.com>
Cc: qemu-devel@nongnu.org, qemu-riscv@nongnu.org
Subject: Re: [PATCH v3 0/3] target/riscv: Support Zve32x and Zve64x extensions
Date: Mon, 29 Apr 2024 13:36:12 +1000 [thread overview]
Message-ID: <CAKmqyKMFE-RrVj1dvsByq-Dbizuz5ZbMrL7+UZjnXBx-DJ83Nw@mail.gmail.com> (raw)
In-Reply-To: <20240328022343.6871-1-jason.chien@sifive.com>
On Thu, Mar 28, 2024 at 12:25 PM Jason Chien <jason.chien@sifive.com> wrote:
>
> This patch series adds the support for Zve32x and Zvx64x and makes vector
> registers visible in GDB if any of the V/Zve*/Zvk* extensions is enabled.
>
> v2:
> Rebase onto riscv-to-apply.next (commit 385e575).
> v3:
> Spuash patch 2 into patch 1.
> Spuash patch 4 into patch 3.
>
> Jason Chien (3):
> target/riscv: Add support for Zve32x extension
> target/riscv: Add support for Zve64x extension
> target/riscv: Relax vector register check in RISCV gdbstub
Thanks!
Applied to riscv-to-apply.next
Alistair
>
> target/riscv/cpu.c | 4 +++
> target/riscv/cpu_cfg.h | 2 ++
> target/riscv/cpu_helper.c | 2 +-
> target/riscv/csr.c | 2 +-
> target/riscv/gdbstub.c | 2 +-
> target/riscv/insn_trans/trans_rvv.c.inc | 4 +--
> target/riscv/tcg/tcg-cpu.c | 33 ++++++++++++++-----------
> 7 files changed, 30 insertions(+), 19 deletions(-)
>
> --
> 2.43.2
>
>
prev parent reply other threads:[~2024-04-29 3:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 2:23 [PATCH v3 0/3] target/riscv: Support Zve32x and Zve64x extensions Jason Chien
2024-03-28 2:23 ` [PATCH v3 1/3] target/riscv: Add support for Zve32x extension Jason Chien
2024-03-28 2:23 ` [PATCH v3 2/3] target/riscv: Add support for Zve64x extension Jason Chien
2024-03-28 2:23 ` [PATCH v3 3/3] target/riscv: Relax vector register check in RISCV gdbstub Jason Chien
2024-04-09 6:29 ` Jason Chien
2024-04-09 6:29 ` [PATCH v3 0/3] target/riscv: Support Zve32x and Zve64x extensions Jason Chien
2024-04-09 9:43 ` Daniel Henrique Barboza
2024-04-29 3:36 ` Alistair Francis [this message]
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=CAKmqyKMFE-RrVj1dvsByq-Dbizuz5ZbMrL7+UZjnXBx-DJ83Nw@mail.gmail.com \
--to=alistair23@gmail.com \
--cc=jason.chien@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 read-only IMAP folder(s) and NNTP newsgroup(s).