From: Andrew Jones <ajones@ventanamicro.com>
To: Himanshu Chauhan <hchauhan@ventanamicro.com>
Cc: qemu-riscv@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH v5 3/3] target/riscv: Enable sdtrig for Ventana's Veyron CPUs
Date: Wed, 13 Mar 2024 20:15:28 +0100 [thread overview]
Message-ID: <20240313-b392d97ea13635ecc7810909@orel> (raw)
In-Reply-To: <20240313182009.608685-4-hchauhan@ventanamicro.com>
On Wed, Mar 13, 2024 at 11:50:09PM +0530, Himanshu Chauhan wrote:
> Ventana's Veyron CPUs support sdtrig ISA extension. By default, enable
> the sdtrig extension and disable the debug property for these CPUs.
>
> Signed-off-by: Himanshu Chauhan <hchauhan@ventanamicro.com>
> ---
> target/riscv/cpu.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/target/riscv/cpu.c b/target/riscv/cpu.c
> index e0710010f5..a7ea66c7fa 100644
> --- a/target/riscv/cpu.c
> +++ b/target/riscv/cpu.c
> @@ -568,7 +568,9 @@ static void rv64_veyron_v1_cpu_init(Object *obj)
> cpu->cfg.ext_zicbom = true;
> cpu->cfg.cbom_blocksize = 64;
> cpu->cfg.cboz_blocksize = 64;
> + cpu->cfg.debug = false;
We don't want/need the above line. Veyron does support 'debug' since it
supports 'sdtrig'. And removing the line above allows all the
'|| cfg->ext_sdtrig' to also be removed.
Thanks,
drew
> cpu->cfg.ext_zicboz = true;
> + cpu->cfg.ext_sdtrig = true;
> cpu->cfg.ext_smaia = true;
> cpu->cfg.ext_ssaia = true;
> cpu->cfg.ext_sscofpmf = true;
> --
> 2.34.1
>
>
prev parent reply other threads:[~2024-03-13 19:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 18:20 [PATCH v5 0/3] Introduce sdtrig ISA extension Himanshu Chauhan
2024-03-13 18:20 ` [PATCH v5 1/3] target/riscv: Enable mcontrol6 triggers only when sdtrig is selected Himanshu Chauhan
2024-03-13 19:06 ` Andrew Jones
2024-03-13 18:20 ` [PATCH v5 2/3] target/riscv: Expose sdtrig ISA extension Himanshu Chauhan
2024-03-13 19:13 ` Andrew Jones
2024-03-13 18:20 ` [PATCH v5 3/3] target/riscv: Enable sdtrig for Ventana's Veyron CPUs Himanshu Chauhan
2024-03-13 19:15 ` Andrew Jones [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=20240313-b392d97ea13635ecc7810909@orel \
--to=ajones@ventanamicro.com \
--cc=hchauhan@ventanamicro.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).