All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
To: Fei Wu <fei2.wu@intel.com>,
	pbonzini@redhat.com, palmer@dabbelt.com,
	alistair.francis@wdc.com, bin.meng@windriver.com,
	liwei1518@gmail.com, dbarboza@ventanamicro.com,
	zhiwei_liu@linux.alibaba.com, qemu-devel@nongnu.org,
	qemu-riscv@nongnu.org, andrei.warkentin@intel.com,
	shaolin.xie@alibaba-inc.com, ved@rivosinc.com,
	sunilvl@ventanamicro.com, haibo1.xu@intel.com,
	evan.chai@intel.com, yin.wang@intel.com,
	tech-server-platform@lists.riscv.org,
	tech-server-soc@lists.riscv.org
Subject: Re: [RFC 0/2] Add RISC-V Server Platform Reference Board
Date: Thu, 7 Mar 2024 23:15:41 +0100	[thread overview]
Message-ID: <ff1b2b2a-dc8e-4346-92de-bee9c4b4b31f@linaro.org> (raw)
In-Reply-To: <20240304102540.2789225-1-fei2.wu@intel.com>

W dniu 4.03.2024 o 11:25, Fei Wu pisze:

> The RISC-V Server Platform specification[1] defines a standardized
> set of hardware and software capabilities, that portable system
> software, such as OS and hypervisors can rely on being present in a
> RISC-V server platform. This patchset provides a RISC-V Server
> Platform (RVSP) reference implementation on qemu which is in
> compliance with the spec as faithful as possible.

I am working on sbsa-ref which is AArch64 Standard Server Platform 
implementation. Will not go through details of rvsp-ref but give some 
potential hints from my work with our platform.


1. Consider versioning the platform.

We have 'platform_version'.'major/minor' exported in 
DeviceTree-formatted data. This allows for firmware to know which of 
non-discoverable hardware features exists and which not. We use it to 
disable XHCI controller on older platform version.


2. If specification allows to have non-discoverable devices then add some.

This will require you to handle them in firmware in some way. Sooner or 
later some physical hardware will be in same situation so they can use 
your firmware code as reference. We have AHCI and XHCI on system bus 
(hardcoded in firmware).


3. You are going to use EDK2 with ACPI. Hide DT from code there with 
some hardware information library.

For sbsa-ref we created SbsaHardwareInfoLib in 
https://openfw.io/edk2-devel/20240306-no-dt-for-cpu-v6-0-acd8727a1b59@linaro.org/ 
patchset.




  parent reply	other threads:[~2024-03-07 22:16 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-04 10:25 [RFC 0/2] Add RISC-V Server Platform Reference Board Fei Wu
2024-03-04 10:25 ` [RFC 1/2] hw/riscv: Add server platform reference machine Fei Wu
2024-03-04 19:35   ` Daniel Henrique Barboza
2024-03-05  5:56     ` Wu, Fei
2024-03-05  9:15       ` Daniel Henrique Barboza
2024-03-06  0:19   ` Alistair Francis
2024-03-06 12:55     ` Wu, Fei
2024-03-06 19:13       ` Atish Kumar Patra
2024-03-07  0:48         ` Alistair Francis
2024-03-07  6:26           ` Wu, Fei
2024-03-08  9:20             ` Andrew Jones
2024-03-11 11:55               ` [RISC-V][tech-server-platform] " Wu, Fei
2024-03-11 14:38                 ` [RISC-V][tech-server-soc] " Andrew Jones
2024-03-12  0:19                   ` Atish Kumar Patra
2024-03-06  0:27   ` Conor Dooley
2024-03-06  2:41     ` Wu, Fei
2024-03-04 10:25 ` [RFC 2/2] target/riscv: Add server platform reference cpu Fei Wu
2024-03-04 19:43   ` Daniel Henrique Barboza
2024-03-05  5:58     ` [RISC-V][tech-server-soc] " Wu, Fei
2024-03-06 13:26       ` Wu, Fei
2024-03-07  7:36         ` Wu, Fei
2024-03-07 12:17           ` [RISC-V][tech-server-platform] " Heinrich Schuchardt
2024-03-07 19:27             ` Daniel Henrique Barboza
2024-03-07 19:15           ` Daniel Henrique Barboza
2024-03-12 12:33             ` Wu, Fei
2024-03-12 12:52               ` Daniel Henrique Barboza
2024-03-04 11:02 ` [RISC-V][tech-server-platform] [RFC 0/2] Add RISC-V Server Platform Reference Board Heinrich Schuchardt
2024-03-04 11:42   ` Chai, Evan
2024-03-07 22:15 ` Marcin Juszkiewicz [this message]
2024-03-12  8:59   ` Wu, Fei

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=ff1b2b2a-dc8e-4346-92de-bee9c4b4b31f@linaro.org \
    --to=marcin.juszkiewicz@linaro.org \
    --cc=alistair.francis@wdc.com \
    --cc=andrei.warkentin@intel.com \
    --cc=bin.meng@windriver.com \
    --cc=dbarboza@ventanamicro.com \
    --cc=evan.chai@intel.com \
    --cc=fei2.wu@intel.com \
    --cc=haibo1.xu@intel.com \
    --cc=liwei1518@gmail.com \
    --cc=palmer@dabbelt.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-riscv@nongnu.org \
    --cc=shaolin.xie@alibaba-inc.com \
    --cc=sunilvl@ventanamicro.com \
    --cc=tech-server-platform@lists.riscv.org \
    --cc=tech-server-soc@lists.riscv.org \
    --cc=ved@rivosinc.com \
    --cc=yin.wang@intel.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.