From: "Gerd Hoffmann" <kraxel@redhat.com>
To: sebastien.boeuf@intel.com
Cc: devel@edk2.groups.io, jiewen.yao@intel.com, jordan.l.justen@intel.com
Subject: Re: [PATCH v3 6/7] OvmfPkg: CloudHv: Rely on PVH memmap instead of CMOS
Date: Fri, 25 Feb 2022 10:41:16 +0100 [thread overview]
Message-ID: <20220225094116.ozgjrwll2negdf2v@sirius.home.kraxel.org> (raw)
In-Reply-To: <38f9fc7d5e5d3ff7ce80f8dd7b57b85f15e3fda6.1645712595.git.sebastien.boeuf@intel.com>
On Thu, Feb 24, 2022 at 03:28:25PM +0100, sebastien.boeuf@intel.com wrote:
> From: Sebastien Boeuf <sebastien.boeuf@intel.com>
>
> Instead of using the CMOS, the CloudHv platform relies on the list of
> memmap entries provided through the PVH boot protocol to determine the
> last RAM address below 4G.
Acked-by: Gerd Hoffmann <kraxel@redhat.com>
next prev parent reply other threads:[~2022-02-25 9:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 14:28 [PATCH v3 0/7] CloudHv: Rely on PVH boot specification Boeuf, Sebastien
2022-02-24 14:28 ` [PATCH v3 1/7] OvmfPkg: Make the Xen ELF header generator more flexible Boeuf, Sebastien
2022-02-25 9:35 ` Gerd Hoffmann
2022-02-24 14:28 ` [PATCH v3 2/7] OvmfPkg: Xen: Use a new fdf include for the PVH ELF header Boeuf, Sebastien
2022-02-25 9:36 ` Gerd Hoffmann
2022-02-24 14:28 ` [PATCH v3 3/7] OvmfPkg: Xen: Generate fdf include file from ELF header generator Boeuf, Sebastien
2022-02-25 9:37 ` [edk2-devel] " Gerd Hoffmann
2022-02-24 14:28 ` [PATCH v3 4/7] OvmfPkg: Generate CloudHv as a PVH ELF binary Boeuf, Sebastien
2022-02-25 9:38 ` Gerd Hoffmann
2022-02-24 14:28 ` [PATCH v3 5/7] OvmfPkg: CloudHv: Retrieve RSDP address from PVH Boeuf, Sebastien
2022-02-25 9:40 ` Gerd Hoffmann
2022-02-24 14:28 ` [PATCH v3 6/7] OvmfPkg: CloudHv: Rely on PVH memmap instead of CMOS Boeuf, Sebastien
2022-02-25 9:41 ` Gerd Hoffmann [this message]
2022-02-24 14:28 ` [PATCH v3 7/7] OvmfPkg: CloudHv: Add README Boeuf, Sebastien
2022-02-25 9:43 ` Gerd Hoffmann
2022-02-25 9:45 ` 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=20220225094116.ozgjrwll2negdf2v@sirius.home.kraxel.org \
--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