From: Andrew Jones <ajones@ventanamicro.com>
To: Fei Wu <fei2.wu@intel.com>
Cc: 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, atishp@rivosinc.com,
conor@kernel.org, heinrich.schuchardt@canonical.com,
marcin.juszkiewicz@linaro.org
Subject: Re: [RFC v2 2/2] hw/riscv: Add server platform reference machine
Date: Mon, 20 May 2024 17:56:19 +0200 [thread overview]
Message-ID: <20240520-2ca42f1c1d9a9c65f5474529@orel> (raw)
In-Reply-To: <20240312135222.3187945-3-fei2.wu@intel.com>
On Tue, Mar 12, 2024 at 09:52:21PM GMT, Fei Wu wrote:
> 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.
>
> A corresponding Qemu RISC-V server platform reference (rvsp-ref for
> short) machine type is added to provide a environment for firmware/OS
> development and testing. The main features included in rvsp-ref are:
>
> - Based on riscv virt machine type
> - A new memory map as close as virt machine as possible
> - A new virt CPU type rvsp-ref-cpu for server platform compliance
> - AIA
> - PCIe AHCI
> - PCIe NIC
We should rebase on the IOMMU series [1] and add an IOMMU to the
platform, as it's required by the Server Soc spec (which is required
by the server platform spec).
[1] https://lore.kernel.org/qemu-devel/20240307160319.675044-1-dbarboza@ventanamicro.com/
Thanks,
drew
next prev parent reply other threads:[~2024-05-20 15:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-12 13:52 [RFC v2 0/2] Add RISC-V Server Platform Reference Board Fei Wu
2024-03-12 13:52 ` [RFC v2 1/2] target/riscv: Add server platform reference cpu Fei Wu
2024-05-20 14:00 ` [RISC-V][tech-server-soc] " Andrew Jones
2024-03-12 13:52 ` [RFC v2 2/2] hw/riscv: Add server platform reference machine Fei Wu
2024-03-22 4:55 ` Alistair Francis
2024-03-22 7:14 ` Marcin Juszkiewicz
2024-03-22 8:50 ` Heinrich Schuchardt
2024-03-22 9:20 ` Marcin Juszkiewicz
2024-03-22 19:10 ` Atish Kumar Patra
2024-03-22 19:14 ` Atish Kumar Patra
2024-03-25 10:06 ` Wu, Fei
2024-05-20 15:56 ` Andrew Jones [this message]
2024-05-21 1:10 ` [RISC-V][tech-server-soc] " Xu, Haibo1
2024-11-26 11:14 ` [RFC v2 0/2] Add RISC-V Server Platform Reference Board Daniel Henrique Barboza
2024-12-09 20:20 ` 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=20240520-2ca42f1c1d9a9c65f5474529@orel \
--to=ajones@ventanamicro.com \
--cc=alistair.francis@wdc.com \
--cc=andrei.warkentin@intel.com \
--cc=atishp@rivosinc.com \
--cc=bin.meng@windriver.com \
--cc=conor@kernel.org \
--cc=dbarboza@ventanamicro.com \
--cc=evan.chai@intel.com \
--cc=fei2.wu@intel.com \
--cc=haibo1.xu@intel.com \
--cc=heinrich.schuchardt@canonical.com \
--cc=liwei1518@gmail.com \
--cc=marcin.juszkiewicz@linaro.org \
--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 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).