Looking at current OvmfPkg today. We have: OvmfPkg\OvmfPkgIa32.fdf OvmfPkg\OvmfPkgIa32X64.fdf OvmfPkg\OvmfPkgX64.fdf OvmfPkg\OvmfXen.fdf OvmfPkg\AmdSev\AmdSevX64.fdf OvmfPkg\Bhyve\BhyveX64.fdf OvmfPkg\Microvm\MicrovmX64.fdf
And we will have OvmfPkg\IntelTdx\IntelTdxX64.fdf soon. I think it is OK to create: OvmfPkg\CloudHv\CloudHvX64.fdf Thank you Yao Jiewen > -----Original Message----- > From: Boeuf, Sebastien <sebastien.bo...@intel.com> > Sent: Monday, January 10, 2022 5:14 PM > To: devel@edk2.groups.io; kra...@redhat.com; Yao, Jiewen > <jiewen....@intel.com> > Subject: Creating new target for Cloud Hypervisor > > Hi all, > > So far I've been able to patch the OvmfPkgX64 target to make it work for both > QEMU and Cloud Hypervisor, but as I try to enable more features (EFI shell for > instance) the gap is getting bigger and harder to keep them working together. > > That's why I'm thinking about creating an OvmfCh target that would be a simple > copy of OvmfX64 at first, and then we could keep improving from there. There > are > multiple things that are not needed by Cloud Hypervisor, which might help > reduce > the complexity of the firmware, eventually leading to faster boot. > > I'd like some confirmation from the community that it's okay to go down this > road > before I proceed and send the patches. > > Thanks, > Sebastien -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#85450): https://edk2.groups.io/g/devel/message/85450 Mute This Topic: https://groups.io/mt/88319600/21656 Group Owner: devel+ow...@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
