From: "Leif Lindholm" <leif@nuviainc.com>
To: "Chang, Abner (HPS SW/FW Technologist)" <abner.chang@hpe.com>
Cc: "Yao, Jiewen" <jiewen.yao@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
gaoliming <gaoliming@byosoft.com.cn>,
'Ard Biesheuvel' <ard.biesheuvel@arm.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
"Ni, Ray" <ray.ni@intel.com>,
"Schaefer, Daniel" <daniel.schaefer@hpe.com>,
'Sunil V L' <sunilvl@ventanamicro.com>,
'Ard Biesheuvel' <ardb+tianocore@kernel.org>,
'Gerd Hoffmann' <kraxel@redhat.com>
Subject: Re: [edk2-devel] [RFC] RISC-V QEMU virtual package
Date: Tue, 7 Sep 2021 18:22:29 +0100 [thread overview]
Message-ID: <20210907172229.geh4zcz7pvxoyyj6@leviathan> (raw)
In-Reply-To: <CS1PR8401MB114482FCC826CE271AB4AF14FFD29@CS1PR8401MB1144.NAMPRD84.PROD.OUTLOOK.COM>
Hi Abner,
Happy to see this happening.
I think the capitalisation should be
RiscVVirtPkg rather than
RiscvVirtPkg though.
More comments below.
On Mon, Sep 06, 2021 at 11:08:47 +0000, Chang, Abner (HPS SW/FW Technologist) wrote:
> We currently only use below modules from ArmVirtPkg,
>
> - ArmVirtPkg/Library
> o FdtPciPcdProducerLib
> o FdtPciHostBridgeLib
>
> - ArmVirtPkg/
> o VirtioFdtDxe
> o FdtClientDxe
> o HighMemDxe
>
> Above modules are related to the extraction of the platform
> configuration from FDT. We also use ArmPkg/DriverArmPciCpuIoDxe, we
> can have RISC-V instance of CpuIoDxe but still leverage PCD produced
> by FdtPciPcdProducerLib.
>
> Another library is QemuFwCfgLib from ArmVirtPkg/Library, I think we
> can have RISC-V own instance because there is a one instance under
> OvmfPkg already.
Are you expecting to need different functionality from the ArmVirtPkg
one? If not, you could move that one to
OvmfPkg/Library/QemuFwCfgCommonLib
or something.
Note that there are also a couple of platforms in edk2-platforms that
reference ArmVirtPkg code. Those would need to be fixed up as well, if
anything they depend on moves.
Agree with comments others made regarding use of git mv of single
module at a time.
I wouldn't mind being a reviewer for the FDT-related common modules.
Regards,
Leif
> 发件人: devel@edk2.groups.io<mailto:devel@edk2.groups.io> <devel@edk2.groups.io<mailto:devel@edk2.groups.io>> 代表 Abner Chang
> 发送时间: 2021年9月5日 11:15
> 收件人: devel@edk2.groups.io<mailto:devel@edk2.groups.io>
> 抄送: Ard Biesheuvel <ard.biesheuvel@arm.com<mailto:ard.biesheuvel@arm.com>>; Michael D Kinney <michael.d.kinney@intel.com<mailto:michael.d.kinney@intel.com>>; Leif Lindholm <leif@nuviainc.com<mailto:leif@nuviainc.com>>; ray.ni@intel.com<mailto:ray.ni@intel.com>; Liming Gao <gaoliming@byosoft.com.cn<mailto:gaoliming@byosoft.com.cn>>; Schaefer, Daniel <daniel.schaefer@hpe.com<mailto:daniel.schaefer@hpe.com>>; Sunil V L <sunilvl@ventanamicro.com<mailto:sunilvl@ventanamicro.com>>
> 主题: [edk2-devel] [RFC] RISC-V QEMU virtual package
>
> Hi all,
> We currently have RISC-V edk2 OVMF package that can boot to Linux kernel on QEMU RISC-V virt platform.
> First at all, we would like to create a folder RiscvVirtPkg under edk2 repo and integrated in the Platform CI build.
>
> Second, RISC-V edk2 OVMF package leverages some edk2 libraries and drivers from ArmVirtPkg, such as FDT related modules for PCI bus, host bridge and etc. We would like to move those generic virtual drivers to
> a common folder for ARM and RISC-V (I don’t think this way is necessary though). Or can we move those to just under OvmfPkg because OvmfPkg also provides some common drivers for the processor architectures.
> Thoughts?
>
> Thanks
> Abner
>
next prev parent reply other threads:[~2021-09-07 17:22 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-05 3:15 [RFC] RISC-V QEMU virtual package Abner Chang
2021-09-06 1:06 ` 回复: [edk2-devel] " gaoliming
2021-09-06 4:16 ` Abner Chang
2021-09-06 6:16 ` Yao, Jiewen
2021-09-06 11:08 ` Abner Chang
2021-09-06 11:44 ` Yao, Jiewen
2021-09-06 12:04 ` Ard Biesheuvel
2021-09-06 12:19 ` Gerd Hoffmann
2021-09-06 13:04 ` Abner Chang
2021-09-07 1:09 ` 回复: " gaoliming
2021-09-07 2:31 ` Abner Chang
2021-09-07 7:18 ` Gerd Hoffmann
2021-09-07 17:22 ` Leif Lindholm [this message]
2021-09-08 12:31 ` Abner Chang
2021-09-08 13:37 ` Gerd Hoffmann
2021-09-08 15:33 ` Abner Chang
2021-09-08 15:53 ` Leif Lindholm
2021-09-09 5:23 ` Gerd Hoffmann
2021-09-10 0:08 ` Abner Chang
2021-09-10 9:54 ` Leif Lindholm
2021-09-10 10:06 ` Ni, Ray
2021-09-11 0:52 ` Abner Chang
[not found] ` <16A39EA413775DFC.29279@groups.io>
2021-09-18 6:46 ` Abner Chang
[not found] ` <16A5D7B7D6218B9A.31588@groups.io>
2021-09-18 7:00 ` Abner Chang
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-list 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=20210907172229.geh4zcz7pvxoyyj6@leviathan \
--to=devel@edk2.groups.io \
/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