public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Yao, Jiewen" <jiewen.yao@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"Yao, Jiewen" <jiewen.yao@intel.com>,
	"Boeuf, Sebastien" <sebastien.boeuf@intel.com>
Cc: "Justen, Jordan L" <jordan.l.justen@intel.com>,
	"kraxel@redhat.com" <kraxel@redhat.com>
Subject: Re: [edk2-devel] [PATCH v6 0/8] CloudHv: Rely on PVH boot specification
Date: Fri, 4 Mar 2022 05:56:09 +0000	[thread overview]
Message-ID: <MW4PR11MB587214B28FC2387F86259ED08C059@MW4PR11MB5872.namprd11.prod.outlook.com> (raw)
In-Reply-To: <16D917C710D2521F.18002@groups.io>

Pushed 26af69d..dd3b1f2
https://github.com/tianocore/edk2/pull/2584

> -----Original Message-----
> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Yao, Jiewen
> Sent: Friday, March 4, 2022 1:55 PM
> To: Boeuf, Sebastien <sebastien.boeuf@intel.com>; devel@edk2.groups.io
> Cc: Justen, Jordan L <jordan.l.justen@intel.com>; kraxel@redhat.com
> Subject: Re: [edk2-devel] [PATCH v6 0/8] CloudHv: Rely on PVH boot
> specification
> 
> Series Reviewed-by: Jiewen.Yao@intel.com.
> 
> > -----Original Message-----
> > From: Boeuf, Sebastien <sebastien.boeuf@intel.com>
> > Sent: Wednesday, March 2, 2022 9:31 PM
> > To: devel@edk2.groups.io
> > Cc: Yao, Jiewen <jiewen.yao@intel.com>; Justen, Jordan L
> > <jordan.l.justen@intel.com>; kraxel@redhat.com; Boeuf, Sebastien
> > <sebastien.boeuf@intel.com>
> > Subject: [PATCH v6 0/8] CloudHv: Rely on PVH boot specification
> >
> > From: Sebastien Boeuf <sebastien.boeuf@intel.com>
> >
> > Cloud Hypervisor aims at emulating the minimal amount of legacy devices
> > and this is why the PVH boot specification is supported. The point is to
> > be able to share some information with the guest without the need for
> > emulating devices that would be present on real hardware.
> >
> > Since Cloud Hypervisor supports loading a PVH ELF binary, the CloudHv
> > target is updated to be generated as such. Relying on the PVH boot
> > specification, we don't need to hardcode the location of the ACPI tables
> > anymore since we can retrieve the RSDP address from the hvm_start_info
> > structure. Same thing for the RAM below 4G, we can find this information
> > through the PVH memmap entries rather than relying on the emulated CMOS.
> >
> > Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
> >
> > Sebastien Boeuf (8):
> >   OvmfPkg: Make the Xen ELF header generator more flexible
> >   OvmfPkg: Xen: Use a new fdf include for the PVH ELF header
> >   OvmfPkg: Xen: Generate fdf include file from ELF header generator
> >   OvmfPkg: CloudHv: Remove VARS and CODE sections
> >   OvmfPkg: Generate CloudHv as a PVH ELF binary
> >   OvmfPkg: CloudHv: Retrieve RSDP address from PVH
> >   OvmfPkg: CloudHv: Rely on PVH memmap instead of CMOS
> >   OvmfPkg: CloudHv: Add README
> >
> >  OvmfPkg/AcpiPlatformDxe/AcpiPlatformDxe.inf |   2 +
> >  OvmfPkg/AcpiPlatformDxe/CloudHvAcpi.c       |  39 ++++--
> >  OvmfPkg/CloudHv/CloudHvElfHeader.fdf.inc    |  54 ++++++++
> >  OvmfPkg/CloudHv/CloudHvX64.dsc              |   2 +-
> >  OvmfPkg/CloudHv/CloudHvX64.fdf              |  40 ++----
> >  OvmfPkg/CloudHv/README                      |  67 ++++++++++
> >  OvmfPkg/Include/IndustryStandard/CloudHv.h  |   5 -
> >  OvmfPkg/OvmfXen.fdf                         |  57 +-------
> >  OvmfPkg/OvmfXenElfHeaderGenerator.c         | 141 +++++++++++++++-----
> >  OvmfPkg/PlatformPei/MemDetect.c             |  73 ++++++++++
> >  OvmfPkg/PlatformPei/PlatformPei.inf         |   2 +
> >  OvmfPkg/XenElfHeader.fdf.inc                |  42 ++++++
> >  12 files changed, 390 insertions(+), 134 deletions(-)
> >  create mode 100644 OvmfPkg/CloudHv/CloudHvElfHeader.fdf.inc
> >  create mode 100644 OvmfPkg/CloudHv/README
> >  create mode 100644 OvmfPkg/XenElfHeader.fdf.inc
> >
> > --
> > 2.32.0
> 
> 
> 
> 
> 


      parent reply	other threads:[~2022-03-04  5:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-02 13:31 [PATCH v6 0/8] CloudHv: Rely on PVH boot specification Boeuf, Sebastien
2022-03-02 13:31 ` [PATCH v6 1/8] OvmfPkg: Make the Xen ELF header generator more flexible Boeuf, Sebastien
2022-03-02 13:31 ` [PATCH v6 2/8] OvmfPkg: Xen: Use a new fdf include for the PVH ELF header Boeuf, Sebastien
2022-03-02 13:31 ` [PATCH v6 3/8] OvmfPkg: Xen: Generate fdf include file from ELF header generator Boeuf, Sebastien
2022-03-02 13:31 ` [PATCH v6 4/8] OvmfPkg: CloudHv: Remove VARS and CODE sections Boeuf, Sebastien
2022-03-03 11:18   ` Gerd Hoffmann
2022-03-02 13:31 ` [PATCH v6 5/8] OvmfPkg: Generate CloudHv as a PVH ELF binary Boeuf, Sebastien
2022-03-03 11:19   ` Gerd Hoffmann
2022-03-02 13:31 ` [PATCH v6 6/8] OvmfPkg: CloudHv: Retrieve RSDP address from PVH Boeuf, Sebastien
2022-03-02 13:31 ` [PATCH v6 7/8] OvmfPkg: CloudHv: Rely on PVH memmap instead of CMOS Boeuf, Sebastien
2022-03-02 13:31 ` [PATCH v6 8/8] OvmfPkg: CloudHv: Add README Boeuf, Sebastien
2022-03-03 11:18   ` Gerd Hoffmann
2022-03-04  5:54 ` [PATCH v6 0/8] CloudHv: Rely on PVH boot specification Yao, Jiewen
     [not found] ` <16D917C710D2521F.18002@groups.io>
2022-03-04  5:56   ` Yao, Jiewen [this message]

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=MW4PR11MB587214B28FC2387F86259ED08C059@MW4PR11MB5872.namprd11.prod.outlook.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