From: "Boeuf, Sebastien" <sebastien.boeuf@intel.com>
To: "kraxel@redhat.com" <kraxel@redhat.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Yao, Jiewen" <jiewen.yao@intel.com>,
"Justen, Jordan L" <jordan.l.justen@intel.com>
Subject: Re: [edk2-devel] [PATCH 1/3] OvmfPkg: Generate CloudHv as a PVH ELF binary
Date: Wed, 23 Feb 2022 17:29:47 +0000 [thread overview]
Message-ID: <a47419e129fa84255e45905b84c1859ba3e60cbf.camel@intel.com> (raw)
In-Reply-To: <d78b66e0d37661565ab6069586d633419f330fde.camel@intel.com>
On Wed, 2022-02-23 at 13:35 +0100, Sebastien Boeuf wrote:
> On Wed, 2022-02-23 at 12:22 +0100, Gerd Hoffmann wrote:
> > On Tue, Feb 22, 2022 at 04:53:04PM +0100, Boeuf, Sebastien wrote:
> > > From: Sebastien Boeuf <sebastien.boeuf@intel.com>
> > >
> > > Following the model from the Xen target, CloudHv is generated as
> > > a
> > > PVH
> > > ELF binary to take advantage of the PVH specification.
> >
> > > --- /dev/null
> > > +++ b/OvmfPkg/CloudHv/CloudHvElfHeaderGenerator.c
> >
> > Why create a new copy of this? What are the differences to the Xen
> > version? I guess they are small so we can maybe have a common
> > ElfPvhHeaderGenerator.c with command line switches?
>
> That's right, I can work on updating the generator to take some
> parameters so that I won't need the duplication of the file.
This has been fixed part of v2 patchset.
>
> >
> > > - OvmfPkg/ResetVector/ResetVector.inf
> > > + OvmfPkg/XenResetVector/XenResetVector.inf
> >
> > Why this is needed?
>
> It stores the "Start of day" structure pointer, which is then used by
> some follow up patches to access hvm_start_info structure (containing
> the PVH boot information).
>
> >
> > > +DATA = {
> > > + #
> > > + # This hex array have been generated by
> > > OvmfPkg/OvmfXenElfHeaderGenerator.c
> > > + # and copied manually.
> >
> > How about having the generator write a .fdf.inc file which you can
> > just
> > include directly without manual copying?
>
> I understand the idea, but do you have any pointer to some existing
> code in the repo already doing such thing?
>
> Thanks,
> Sebastien
>
> >
> > take care,
> > Gerd
> >
>
---------------------------------------------------------------------
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-02-23 17:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1645542995.git.sebastien.boeuf@intel.com>
2022-02-22 15:53 ` [PATCH 1/3] OvmfPkg: Generate CloudHv as a PVH ELF binary Boeuf, Sebastien
2022-02-23 11:22 ` [edk2-devel] " Gerd Hoffmann
2022-02-23 12:35 ` Boeuf, Sebastien
2022-02-23 17:29 ` Boeuf, Sebastien [this message]
2022-02-24 6:27 ` Gerd Hoffmann
2022-02-24 14:35 ` Boeuf, Sebastien
2022-02-22 15:53 ` [PATCH 2/3] OvmfPkg: CloudHv: Retrieve RSDP address from PVH Boeuf, Sebastien
2022-02-23 11:31 ` [edk2-devel] " Gerd Hoffmann
2022-02-24 14:41 ` Boeuf, Sebastien
2022-02-25 9:34 ` Gerd Hoffmann
2022-02-22 15:53 ` [PATCH 3/3] OvmfPkg: CloudHv: Rely on PVH memmap instead of CMOS Boeuf, Sebastien
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=a47419e129fa84255e45905b84c1859ba3e60cbf.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