From: Nicholas Piggin <npiggin@gmail.com>
To: Daniel Henrique Barboza <daniel.barboza@oss.qualcomm.com>
Cc: qemu-devel@nongnu.org, qemu-riscv@nongnu.org,
alistair.francis@wdc.com, liwei1518@gmail.com,
zhiwei_liu@linux.alibaba.com, chao.liu.zevorn@gmail.com,
leif.lindholm@oss.qualcomm.com, andrew.jones@oss.qualcomm.com,
Fei Wu <wu.fei9@sanechips.com.cn>
Subject: Re: [PATCH v6 2/4] target/riscv: Add server platform reference cpu
Date: Sat, 16 May 2026 04:15:48 +1000 [thread overview]
Message-ID: <agdgwnLqvEeMoeqk@lima-default> (raw)
In-Reply-To: <20260514204640.2540054-3-daniel.barboza@oss.qualcomm.com>
On Thu, May 14, 2026 at 05:46:38PM -0300, Daniel Henrique Barboza wrote:
> From: Fei Wu <wu.fei9@sanechips.com.cn>
>
> The harts requirements of RISC-V server platform [1] require RVA23 ISA
> profile support and others.
>
> This patch provides a new "riscv-server-ref" CPU to go along with the
> future "riscv-server-ref" board.
About compatibility, if we get a server platform spec v2.0 that requires
a different machine and RVA28 + Sxxx CPU. Is the plan to update these,
or add a new CPU and machine types? If the latter, then perhaps a
version in the names like riscv-server-v1.0 / riscv-server-v1.0-cpu
would be good.
Non-versioned names could be aliases to the latest one, but I don't know
if that is really worthwhile particularly for non virtualized system.
Thanks,
Nick
next prev parent reply other threads:[~2026-05-15 18:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-14 20:46 [PATCH v6 0/4] hw/riscv: Server Platform Reference Board Daniel Henrique Barboza
2026-05-14 20:46 ` [PATCH v6 1/4] target/riscv/cpu.c: remove 'bare' condition for .profile Daniel Henrique Barboza
2026-05-15 3:13 ` Chao Liu
2026-05-14 20:46 ` [PATCH v6 2/4] target/riscv: Add server platform reference cpu Daniel Henrique Barboza
2026-05-15 3:14 ` Chao Liu
2026-05-15 18:15 ` Nicholas Piggin [this message]
2026-05-15 19:54 ` Daniel Henrique Barboza
2026-05-14 20:46 ` [PATCH v6 3/4] hw/riscv: server platform reference machine Daniel Henrique Barboza
2026-05-15 3:14 ` Chao Liu
2026-05-14 20:46 ` [PATCH v6 4/4] docs: add riscv-server-ref.rst 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=agdgwnLqvEeMoeqk@lima-default \
--to=npiggin@gmail.com \
--cc=alistair.francis@wdc.com \
--cc=andrew.jones@oss.qualcomm.com \
--cc=chao.liu.zevorn@gmail.com \
--cc=daniel.barboza@oss.qualcomm.com \
--cc=leif.lindholm@oss.qualcomm.com \
--cc=liwei1518@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=wu.fei9@sanechips.com.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.