From: Alistair Francis <alistair23@gmail.com>
To: Daniel Henrique Barboza <dbarboza@ventanamicro.com>
Cc: qemu-devel@nongnu.org, qemu-riscv@nongnu.org,
alistair.francis@wdc.com, bmeng@tinylab.org,
liwei1518@gmail.com, zhiwei_liu@linux.alibaba.com,
palmer@rivosinc.com, richard.henderson@linaro.org
Subject: Re: [PATCH for-9.1 v3 0/2] target/riscv: set tval in breakpoints
Date: Mon, 29 Apr 2024 13:16:38 +1000 [thread overview]
Message-ID: <CAKmqyKNjNfCcLQUzOxKOxswC4m7vZ1n1nVPgEuRaZVZJqt+ynA@mail.gmail.com> (raw)
In-Reply-To: <20240416230437.1869024-1-dbarboza@ventanamicro.com>
On Wed, Apr 17, 2024 at 9:05 AM Daniel Henrique Barboza
<dbarboza@ventanamicro.com> wrote:
>
> Hi,
>
> This new version has a change suggested by Richard in v2. No other
> changes made.
>
> Changes from v2:
> - patch 2:
> - use tcg_constant_tl() instead of loading a temp and doing a
> movi_tl()
> - v2 link: https://lore.kernel.org/qemu-riscv/20240416194132.1843699-1-dbarboza@ventanamicro.com/
>
>
> Daniel Henrique Barboza (2):
> target/riscv/debug: set tval=pc in breakpoint exceptions
> trans_privileged.c.inc: set (m|s)tval on ebreak breakpoint
Thanks!
Applied to riscv-to-apply.next
Alistair
>
> target/riscv/cpu_helper.c | 1 +
> target/riscv/debug.c | 3 +++
> target/riscv/insn_trans/trans_privileged.c.inc | 2 ++
> 3 files changed, 6 insertions(+)
>
> --
> 2.44.0
>
>
prev parent reply other threads:[~2024-04-29 3:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 23:04 [PATCH for-9.1 v3 0/2] target/riscv: set tval in breakpoints Daniel Henrique Barboza
2024-04-16 23:04 ` [PATCH for-9.1 v3 1/2] target/riscv/debug: set tval=pc in breakpoint exceptions Daniel Henrique Barboza
2024-04-26 1:39 ` LIU Zhiwei
2024-04-29 3:08 ` Alistair Francis
2024-04-16 23:04 ` [PATCH for-9.1 v3 2/2] trans_privileged.c.inc: set (m|s)tval on ebreak breakpoint Daniel Henrique Barboza
2024-04-17 2:40 ` Richard Henderson
2024-04-26 1:40 ` LIU Zhiwei
2024-04-29 3:09 ` Alistair Francis
2024-04-29 3:16 ` 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=CAKmqyKNjNfCcLQUzOxKOxswC4m7vZ1n1nVPgEuRaZVZJqt+ynA@mail.gmail.com \
--to=alistair23@gmail.com \
--cc=alistair.francis@wdc.com \
--cc=bmeng@tinylab.org \
--cc=dbarboza@ventanamicro.com \
--cc=liwei1518@gmail.com \
--cc=palmer@rivosinc.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=zhiwei_liu@linux.alibaba.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 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).