All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Henrique Barboza <daniel.barboza@oss.qualcomm.com>
To: Nicholas Piggin <npiggin@gmail.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: Fri, 15 May 2026 16:54:43 -0300	[thread overview]
Message-ID: <174f03b2-b979-47d2-aec8-645d797ab758@oss.qualcomm.com> (raw)
In-Reply-To: <agdgwnLqvEeMoeqk@lima-default>



On 5/15/2026 3:15 PM, Nicholas Piggin wrote:
> 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.

Good question.  We can get away with machine props to change the board
behavior based on spec version but not sure if this makes sense with
a CPU.  I suppose we could live with:

-cpu riscv-server-ref,spec1.1=on

to change the CPU setup to v1.1 and so on, but creating a new CPU with the
spec version in the name like you suggested (e.g. riscv-server-ref-v1.1)
seems cleaner.  In particular if the spec doesn't change that much - which
I guess it's fair to assume given that a reference spec wouldn't be much
of a reference if it keeps changing/updating all the time ...


Thanks,
Daniel

> 
> 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



  reply	other threads:[~2026-05-15 19:55 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
2026-05-15 19:54     ` Daniel Henrique Barboza [this message]
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=174f03b2-b979-47d2-aec8-645d797ab758@oss.qualcomm.com \
    --to=daniel.barboza@oss.qualcomm.com \
    --cc=alistair.francis@wdc.com \
    --cc=andrew.jones@oss.qualcomm.com \
    --cc=chao.liu.zevorn@gmail.com \
    --cc=leif.lindholm@oss.qualcomm.com \
    --cc=liwei1518@gmail.com \
    --cc=npiggin@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.