From: "Boeuf, Sebastien" <sebastien.boeuf@intel.com>
To: "kraxel@redhat.com" <kraxel@redhat.com>,
"Yao, Jiewen" <jiewen.yao@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Re: Creating new target for Cloud Hypervisor
Date: Mon, 10 Jan 2022 10:45:43 +0000 [thread overview]
Message-ID: <a926a392c38ed9ecedbb0f1c7d26642039bf8a51.camel@intel.com> (raw)
In-Reply-To: <MW4PR11MB587218A5A4F341659D73D96D8C509@MW4PR11MB5872.namprd11.prod.outlook.com>
On Mon, 2022-01-10 at 10:35 +0000, Yao, Jiewen wrote:
> 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
Sounds good, I'll start working on this.
>
> Thank you
> Yao Jiewen
>
> > -----Original Message-----
> > From: Boeuf, Sebastien <sebastien.boeuf@intel.com>
> > Sent: Monday, January 10, 2022 5:14 PM
> > To: devel@edk2.groups.io; kraxel@redhat.com; Yao, Jiewen
> > <jiewen.yao@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
---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: "Les Montalets"- 2, rue de Paris,
92196 Meudon Cedex, France
Registration Number: 302 456 199 R.C.S. NANTERRE
Capital: 4,572,000 Euros
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
next prev parent reply other threads:[~2022-01-10 10:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 9:13 Creating new target for Cloud Hypervisor Boeuf, Sebastien
2022-01-10 10:35 ` Yao, Jiewen
2022-01-10 10:45 ` Boeuf, Sebastien [this message]
2022-01-10 10:45 ` Gerd Hoffmann
2022-01-10 11:03 ` Boeuf, Sebastien
2022-01-10 11:54 ` Gerd Hoffmann
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=a926a392c38ed9ecedbb0f1c7d26642039bf8a51.camel@intel.com \
--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