From: "Peter Grehan" <grehan@freebsd.org>
To: devel@edk2.groups.io
Subject: Re: [PATCH v2 0/2] OvmfPkg/Bhyve: Fix Bhyve build following breaking changes in OvmfPkg
Date: Thu, 12 Nov 2020 18:40:12 +1000 [thread overview]
Message-ID: <4d994248-a885-7bc2-a396-9c72792f1b15@freebsd.org> (raw)
In-Reply-To: <20201112053153.22038-1-rebecca@bsdio.com>
Acked-by: Peter Grehan <grehan@freebsd.org>
> Fix Bhyve following breaking changes in OvmfPkg.
> Follows suggestions from Laszlo in the v1 patch set.
> I also changed the INF version in ResetVector.inf to 1.29.
>
> Rebecca Cran (2):
> OvmfPkg/Bhyve: detach ResetVector from before the SEV-ES changes
> OvmfPkg/Bhyve: fix build breakage after SEV-ES changes
>
> OvmfPkg/Bhyve/BhyveX64.dsc | 3 +-
> OvmfPkg/Bhyve/BhyveX64.fdf | 2 +-
> OvmfPkg/Bhyve/ResetVector/ResetVector.inf | 38 +++++
> .../Bhyve/ResetVector/Ia32/PageTables64.asm | 149 ++++++++++++++++++
> OvmfPkg/Bhyve/ResetVector/ResetVector.nasmb | 68 ++++++++
> 5 files changed, 258 insertions(+), 2 deletions(-)
> create mode 100644 OvmfPkg/Bhyve/ResetVector/ResetVector.inf
> create mode 100644 OvmfPkg/Bhyve/ResetVector/Ia32/PageTables64.asm
> create mode 100644 OvmfPkg/Bhyve/ResetVector/ResetVector.nasmb
>
next prev parent reply other threads:[~2020-11-12 8:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-12 5:31 [PATCH v2 0/2] OvmfPkg/Bhyve: Fix Bhyve build following breaking changes in OvmfPkg Rebecca Cran
2020-11-12 5:31 ` [PATCH v2 1/2] OvmfPkg/Bhyve: detach ResetVector from before the SEV-ES changes Rebecca Cran
2020-11-12 5:31 ` [PATCH v2 2/2] OvmfPkg/Bhyve: fix build breakage after " Rebecca Cran
2020-11-12 8:40 ` Peter Grehan [this message]
2020-11-13 23:18 ` [edk2-devel] [PATCH v2 0/2] OvmfPkg/Bhyve: Fix Bhyve build following breaking changes in OvmfPkg Laszlo Ersek
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=4d994248-a885-7bc2-a396-9c72792f1b15@freebsd.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