On Thu, 2022-02-24 at 07:27 +0100, Gerd Hoffmann wrote:
> > > > +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
> > > c
> > > +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 t
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
> > >
> > > Following the model from the Xen target, CloudHv is generated as
> > >
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
> >
> > Following the model from the Xen target, CloudHv is generated as a
> > PVH
> > ELF binary to take advantage of the PVH specification.
>
>
On Tue, Feb 22, 2022 at 04:53:04PM +0100, Boeuf, Sebastien wrote:
> From: Sebastien Boeuf
>
> 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 c
From: Sebastien Boeuf
Following the model from the Xen target, CloudHv is generated as a PVH
ELF binary to take advantage of the PVH specification.
Signed-off-by: Sebastien Boeuf
---
OvmfPkg/CloudHv/CloudHvElfHeaderGenerator.c | 150
OvmfPkg/CloudHv/CloudHvX64.dsc
