From: Bin Meng <bmeng.cn@gmail.com>
To: Frank Chang <frank.chang@sifive.com>
Cc: "qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
"open list:RISC-V" <qemu-riscv@nongnu.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Alistair Francis <alistair.francis@wdc.com>,
Bin Meng <bin.meng@windriver.com>
Subject: Re: [PATCH 7/9] target/riscv: debug: Check VU/VS modes for type 2 trigger
Date: Wed, 15 Jun 2022 20:43:54 +0800 [thread overview]
Message-ID: <CAEUhbmV7aom2Y6ZGs4hsv2MGbAX_uc10_YzChvcGoF0Qg0-h3A@mail.gmail.com> (raw)
In-Reply-To: <20220610051328.7078-8-frank.chang@sifive.com>
On Fri, Jun 10, 2022 at 1:25 PM <frank.chang@sifive.com> wrote:
>
> From: Frank Chang <frank.chang@sifive.com>
>
> Type 2 trigger cannot be fired in VU/VS modes.
>
> Signed-off-by: Frank Chang <frank.chang@sifive.com>
> ---
> target/riscv/debug.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
next prev parent reply other threads:[~2022-06-15 12:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 5:13 [PATCH 0/9] Improve RISC-V Debug support frank.chang
2022-06-10 5:13 ` [PATCH 1/9] target/riscv: debug: Determine the trigger type from tdata1.type frank.chang
2022-06-15 5:33 ` Bin Meng
2022-06-15 5:41 ` Bin Meng
2022-06-10 5:13 ` [PATCH 2/9] target/riscv: debug: Introduce build_tdata1() to build tdata1 register content frank.chang
2022-06-15 12:05 ` Bin Meng
2022-06-10 5:13 ` [PATCH 3/9] target/riscv: debug: Introduce tdata1, tdata2, and tdata3 CSRs frank.chang
2022-06-15 12:17 ` Bin Meng
2022-06-10 5:13 ` [PATCH 4/9] target/riscv: debug: Restrict the range of tselect value can be written frank.chang
2022-06-15 12:21 ` Bin Meng
2022-06-10 5:13 ` [PATCH 5/9] target/riscv: debug: Introduce tinfo CSR frank.chang
2022-06-15 12:26 ` Bin Meng
2022-06-10 5:13 ` [PATCH 6/9] target/riscv: debug: Create common trigger actions function frank.chang
2022-06-15 12:41 ` Bin Meng
2022-06-10 5:13 ` [PATCH 7/9] target/riscv: debug: Check VU/VS modes for type 2 trigger frank.chang
2022-06-15 12:43 ` Bin Meng [this message]
2022-06-10 5:13 ` [PATCH 8/9] target/riscv: debug: Return 0 if previous value written to tselect >= number of triggers frank.chang
2022-06-15 13:17 ` Bin Meng
2022-06-10 5:13 ` [PATCH 9/9] target/riscv: debug: Add initial support of type 6 trigger frank.chang
2022-06-15 13:18 ` Bin Meng
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=CAEUhbmV7aom2Y6ZGs4hsv2MGbAX_uc10_YzChvcGoF0Qg0-h3A@mail.gmail.com \
--to=bmeng.cn@gmail.com \
--cc=alistair.francis@wdc.com \
--cc=bin.meng@windriver.com \
--cc=frank.chang@sifive.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).