From: Bin Meng <bmeng.cn@gmail.com>
To: Alistair Francis <alistair.francis@wdc.com>,
qemu-devel@nongnu.org, qemu-riscv@nongnu.org
Cc: Richard Henderson <richard.henderson@linaro.org>
Subject: [PATCH v2 6/7] target/riscv: cpu: Enable native debug feature on virt and sifive_u CPUs
Date: Sat, 30 Oct 2021 21:55:12 +0800 [thread overview]
Message-ID: <20211030135513.18517-7-bin.meng@windriver.com> (raw)
In-Reply-To: <20211030135513.18517-1-bin.meng@windriver.com>
Turn on native debug feature on virt and sifive_u CPUs.
Signed-off-by: Bin Meng <bin.meng@windriver.com>
---
Changes in v2:
- new patch: enable native debug feature on virt and sifive_u CPUs
target/riscv/cpu.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/target/riscv/cpu.c b/target/riscv/cpu.c
index 6f69ef4f50..b4d3c58dea 100644
--- a/target/riscv/cpu.c
+++ b/target/riscv/cpu.c
@@ -153,6 +153,7 @@ static void rv64_base_cpu_init(Object *obj)
CPURISCVState *env = &RISCV_CPU(obj)->env;
/* We set this in the realise function */
set_misa(env, MXL_RV64, 0);
+ qdev_prop_set_bit(DEVICE(obj), "debug", true);
}
static void rv64_sifive_u_cpu_init(Object *obj)
@@ -160,6 +161,7 @@ static void rv64_sifive_u_cpu_init(Object *obj)
CPURISCVState *env = &RISCV_CPU(obj)->env;
set_misa(env, MXL_RV64, RVI | RVM | RVA | RVF | RVD | RVC | RVS | RVU);
set_priv_version(env, PRIV_VERSION_1_10_0);
+ qdev_prop_set_bit(DEVICE(obj), "debug", true);
}
static void rv64_sifive_e_cpu_init(Object *obj)
@@ -175,6 +177,7 @@ static void rv32_base_cpu_init(Object *obj)
CPURISCVState *env = &RISCV_CPU(obj)->env;
/* We set this in the realise function */
set_misa(env, MXL_RV32, 0);
+ qdev_prop_set_bit(DEVICE(obj), "debug", true);
}
static void rv32_sifive_u_cpu_init(Object *obj)
@@ -182,6 +185,7 @@ static void rv32_sifive_u_cpu_init(Object *obj)
CPURISCVState *env = &RISCV_CPU(obj)->env;
set_misa(env, MXL_RV32, RVI | RVM | RVA | RVF | RVD | RVC | RVS | RVU);
set_priv_version(env, PRIV_VERSION_1_10_0);
+ qdev_prop_set_bit(DEVICE(obj), "debug", true);
}
static void rv32_sifive_e_cpu_init(Object *obj)
--
2.25.1
next prev parent reply other threads:[~2021-10-30 13:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-30 13:55 [PATCH v2 0/7] target/riscv: Initial support for native debug feature via M-mode CSRs Bin Meng
2021-10-30 13:55 ` [PATCH v2 1/7] target/riscv: Add initial support for native debug Bin Meng
2021-10-30 13:55 ` [PATCH v2 2/7] target/riscv: machine: Add debug state description Bin Meng
2021-11-17 0:50 ` Alistair Francis
2021-10-30 13:55 ` [PATCH v2 3/7] target/riscv: debug: Implement debug related TCGCPUOps Bin Meng
2021-11-17 0:54 ` Alistair Francis
2021-10-30 13:55 ` [PATCH v2 4/7] target/riscv: cpu: Add a config option for native debug Bin Meng
2021-11-03 5:59 ` Alistair Francis
2021-10-30 13:55 ` [PATCH v2 5/7] target/riscv: csr: Hook debug CSR read/write Bin Meng
2021-11-17 0:56 ` Alistair Francis
2021-10-30 13:55 ` Bin Meng [this message]
2021-11-17 0:57 ` [PATCH v2 6/7] target/riscv: cpu: Enable native debug feature on virt and sifive_u CPUs Alistair Francis
2021-11-17 9:51 ` Bin Meng
2021-10-30 13:55 ` [PATCH v2 7/7] hw/core: tcg-cpu-ops.h: Update comments of debug_check_watchpoint() Bin Meng
2021-11-03 6:00 ` 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=20211030135513.18517-7-bin.meng@windriver.com \
--to=bmeng.cn@gmail.com \
--cc=alistair.francis@wdc.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=richard.henderson@linaro.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).