All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Henrique Barboza <dbarboza@ventanamicro.com>
To: Alvin Chang <alvinga@andestech.com>,
	qemu-riscv@nongnu.org, qemu-devel@nongnu.org
Cc: alistair.francis@wdc.com, bin.meng@windriver.com,
	liwei1518@gmail.com, zhiwei_liu@linux.alibaba.com,
	vivahavey@gmail.com, Yu-Ming Chang <yumin686@andestech.com>
Subject: Re: [PATCH v2 1/2] target/riscv: Add "debug-1.0" to specify debug specification v1.0
Date: Fri, 28 Nov 2025 08:32:42 -0300	[thread overview]
Message-ID: <a50869b2-d348-42e4-abec-d47dea8587f2@ventanamicro.com> (raw)
In-Reply-To: <20251126164329.2157287-2-alvinga@andestech.com>



On 11/26/25 1:43 PM, Alvin Chang wrote:
> Currently RISC-V CPU has a property "debug" which is equivalent to old
> debug specification v0.13 version. Now we have ratified debug
> specification v1.0 version. To support both versions, we add "debug-1.0"
> as one of RISC-V CPU property to let user specify that debug v0.13 or
> debug v1.0 is enabled. When debug-1.0=false CPU fallbacks to default
> v0.13 version.
> 
> Note that "debug-1.0" depends on "debug" property:
> - debug=false,debug-1.0={true|false} --> debug is disabled
> - debug=true,debug-1.0=false         --> debug v0.13 is enabled
> - debug=true,debug-1.0=true          --> debug v1.0  is enabled


It is worth noticing that 'debug' is default true, so setting debug-1.0=true alone
is enough to enable debug v1.0.

If a new version becomes necessary we can add this clarification in the commit msg.


Reviewed-by: Daniel Henrique Barboza <dbarboza@ventanamicro.com>

> 
> Signed-off-by: Alvin Chang <alvinga@andestech.com>
> Reviewed-by: Yu-Ming Chang <yumin686@andestech.com>
> ---
>   target/riscv/cpu.c                | 1 +
>   target/riscv/cpu_cfg_fields.h.inc | 1 +
>   2 files changed, 2 insertions(+)
> 
> diff --git a/target/riscv/cpu.c b/target/riscv/cpu.c
> index 73d4280..082035b 100644
> --- a/target/riscv/cpu.c
> +++ b/target/riscv/cpu.c
> @@ -2637,6 +2637,7 @@ RISCVCPUImpliedExtsRule *riscv_multi_ext_implied_rules[] = {
>   
>   static const Property riscv_cpu_properties[] = {
>       DEFINE_PROP_BOOL("debug", RISCVCPU, cfg.debug, true),
> +    DEFINE_PROP_BOOL("debug-1.0", RISCVCPU, cfg.debug_1_00, false),
>   
>       {.name = "pmu-mask", .info = &prop_pmu_mask},
>       {.name = "pmu-num", .info = &prop_pmu_num}, /* Deprecated */
> diff --git a/target/riscv/cpu_cfg_fields.h.inc b/target/riscv/cpu_cfg_fields.h.inc
> index a154ecd..402b255 100644
> --- a/target/riscv/cpu_cfg_fields.h.inc
> +++ b/target/riscv/cpu_cfg_fields.h.inc
> @@ -151,6 +151,7 @@ BOOL_FIELD(ext_XVentanaCondOps)
>   BOOL_FIELD(mmu)
>   BOOL_FIELD(pmp)
>   BOOL_FIELD(debug)
> +BOOL_FIELD(debug_1_00)
>   BOOL_FIELD(misa_w)
>   
>   BOOL_FIELD(short_isa_string)



  reply	other threads:[~2025-11-28 11:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-26 16:43 [PATCH v2 0/2] RISC-V: Initial support versioning of debug specification Alvin Chang via
2025-11-26 16:43 ` [PATCH v2 1/2] target/riscv: Add "debug-1.0" to specify debug specification v1.0 Alvin Chang via
2025-11-28 11:32   ` Daniel Henrique Barboza [this message]
2025-11-26 16:43 ` [PATCH v2 2/2] target/riscv: Simpily support versioning of debug trigger module Alvin Chang via
2025-11-28 11:38   ` Daniel Henrique Barboza

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=a50869b2-d348-42e4-abec-d47dea8587f2@ventanamicro.com \
    --to=dbarboza@ventanamicro.com \
    --cc=alistair.francis@wdc.com \
    --cc=alvinga@andestech.com \
    --cc=bin.meng@windriver.com \
    --cc=liwei1518@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-riscv@nongnu.org \
    --cc=vivahavey@gmail.com \
    --cc=yumin686@andestech.com \
    --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 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.