From: Andrew Jones <ajones@ventanamicro.com>
To: Daniel Henrique Barboza <dbarboza@ventanamicro.com>
Cc: Chao Liu <chao.liu.riscv@isrc.iscas.ac.cn>,
alistair.francis@wdc.com, liwei1518@gmail.com,
palmer@dabbelt.com, qemu-devel@nongnu.org, qemu-riscv@nongnu.org,
wu.fei9@sanechips.com.cn, zhiwei_liu@linux.alibaba.com,
xiaofan@iscas.ac.cn, wangjingwei@iscas.ac.cn
Subject: Re: [PATCH v4 3/5] hw/riscv: experimental server platform reference machine
Date: Tue, 25 Nov 2025 09:39:10 -0600 [thread overview]
Message-ID: <20251125-3e644247d1d73ebad131f69a@orel> (raw)
In-Reply-To: <ef829d73-f39c-421a-8ebd-ef5422a7fedc@ventanamicro.com>
On Tue, Nov 25, 2025 at 08:24:22AM -0300, Daniel Henrique Barboza wrote:
...
> So, in the latest spec, section 2.1 RISC-V Harts:
>
> https://github.com/riscv-non-isa/riscv-server-platform/releases/download/v0.9-rc3/riscv-server-platform.pdf
>
> There's a set of "rules" that each hart should or can follow. Rule RVA_010 states:
>
> "The RISC-V application processor harts in the SoC MUST support the RVA23S64 ISA
> profile [6]."
>
> The next rule, RVA_020:
>
> "The RISC-V application processor harts in the SoC MUST support the following
> extensions:
> - Sv48
> - Sdtrig [7]
> - Sdext [7]
> - Zkr
> - Ssccfg
> - Ssstrict [6]
> - Ssaia [8]"
>
>
> I take it that the wording used, **MUST**, indicates that RVA_020 is mandatory so we should
> in fact support sv48. In this case we can change the default to sv48 without problems
>
>
> Drew, is this a fair interpretation? Thanks,
Yes. The server platform spec is based on rva23, but also mandates
additional extensions beyond what's mandated by the profile, including
sv48. (And this is why I stated the default should be sv48 when pointing
out that it shouldn't be sv57[1]).
[1] https://lore.kernel.org/all/20251111-e4f4062f326aef78ef820d00@orel/
Thanks,
drew
next prev parent reply other threads:[~2025-11-25 15:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-11 18:29 [PATCH v4 0/5] hw/riscv: Experimental Server Platform Reference Board Daniel Henrique Barboza
2025-11-11 18:29 ` [PATCH v4 1/5] target/riscv/cpu.c: remove 'bare' condition for .profile Daniel Henrique Barboza
2025-11-24 2:02 ` Chao Liu
2025-11-11 18:29 ` [PATCH v4 2/5] target/riscv: Add server platform reference cpu Daniel Henrique Barboza
2025-11-11 23:05 ` Andrew Jones
2025-11-17 17:57 ` Daniel Henrique Barboza
2025-11-11 18:29 ` [PATCH v4 3/5] hw/riscv: experimental server platform reference machine Daniel Henrique Barboza
2025-11-11 23:36 ` Andrew Jones
2025-11-18 20:15 ` Daniel Henrique Barboza
2025-11-18 20:50 ` Andrew Jones
2025-11-12 7:13 ` Philippe Mathieu-Daudé
2025-11-24 1:56 ` Chao Liu
2025-11-25 11:24 ` Daniel Henrique Barboza
2025-11-25 15:39 ` Andrew Jones [this message]
2025-12-04 5:37 ` Anup Patel
2025-11-11 18:29 ` [PATCH v4 4/5] hw/riscv/server_platform_ref.c: add riscv-iommu-sys Daniel Henrique Barboza
2025-11-12 7:13 ` Philippe Mathieu-Daudé
2025-11-11 18:29 ` [PATCH v4 5/5] docs: add rvsp-ref.rst Daniel Henrique Barboza
2025-11-11 23:39 ` Andrew Jones
2025-11-24 2:06 ` Chao Liu
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=20251125-3e644247d1d73ebad131f69a@orel \
--to=ajones@ventanamicro.com \
--cc=alistair.francis@wdc.com \
--cc=chao.liu.riscv@isrc.iscas.ac.cn \
--cc=dbarboza@ventanamicro.com \
--cc=liwei1518@gmail.com \
--cc=palmer@dabbelt.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=wangjingwei@iscas.ac.cn \
--cc=wu.fei9@sanechips.com.cn \
--cc=xiaofan@iscas.ac.cn \
--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.