From: "Ard Biesheuvel" <ardb@kernel.org>
To: devel@edk2.groups.io, gary.lin@hpe.com
Cc: Ard Biesheuvel <ardb+tianocore@kernel.org>,
Jiewen Yao <jiewen.yao@intel.com>,
Jordan Justen <jordan.l.justen@intel.com>,
Gerd Hoffmann <kraxel@redhat.com>,
Anthony Perard <anthony.perard@citrix.com>,
Julien Grall <julien@xen.org>, Jim Fehlig <jfehlig@suse.com>,
Joey Li <jlee@suse.com>
Subject: Re: [edk2-devel] [RESEND PATCH v3 0/4] Fix OvmfXen boot failure due to s3 support state
Date: Tue, 31 Aug 2021 13:08:52 +0200 [thread overview]
Message-ID: <CAMj1kXHUHt=0+L7=ToY-WW1a7WgXeFisqn6oZHVjFuSUegLrvA@mail.gmail.com> (raw)
In-Reply-To: <20210831013115.23110-1-gary.lin@hpe.com>
On Tue, 31 Aug 2021 at 03:31, Lin, Gary (HPS OE-Linux) <gary.lin@hpe.com> wrote:
>
> When using HVM Direct kernel boot with OvmfXen, it could fail at the
> S3BootScript due to the inconsistency between QemuFwCfgS3Enabled()
> and PcdAcpiS3Enable.
>
> This patch series initializes PcdAcpiS3Enable in
> . Besides, QemuFwCfgS3Enabled() is
> replaced with PcdAcpiS3Enable in several OVMF libraries to avoid the
> potential inconsistency.
>
> Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=3573
>
> v3:
> - Update the description per Anthony's suggestion
> - Add the bugzilla links
> - Move the QemuKernelLoaderFsDxe patch out of this patch series
> and make it an independent patch
> v2:
> - Amend the description and address "HVM Direct Kernel Boot"
> - Add the comment for the conditional test of QemuFwCfgS3Enabled()
> - Remove unused QemuFwCfgLib
> - Update my email address
>
> Cc: Ard Biesheuvel <ardb+tianocore@kernel.org>
> Cc: Jiewen Yao <jiewen.yao@intel.com>
> Cc: Jordan Justen <jordan.l.justen@intel.com>
> Cc: Gerd Hoffmann <kraxel@redhat.com>
> Cc: Anthony Perard <anthony.perard@citrix.com>
> Cc: Julien Grall <julien@xen.org>
> Cc: Jim Fehlig <jfehlig@suse.com>
> Cc: Joey Li <jlee@suse.com>
>
> Gary Lin (4):
> OvmfPkg/OvmfXen: set PcdAcpiS3Enable at initialization
> OvmfPkg/LockBoxLib: use PcdAcpiS3Enable to detect S3 support
> OvmfPkg/PlatformBootManagerLib: use PcdAcpiS3Enable to detect S3
> support
> OvmfPkg/SmmControl2Dxe: use PcdAcpiS3Enable to detect S3 support
>
Merged as #1933
Thanks,
> OvmfPkg/Library/LockBoxLib/LockBoxDxeLib.inf | 3 +--
> .../PlatformBootManagerLib.inf | 1 +
> OvmfPkg/SmmControl2Dxe/SmmControl2Dxe.inf | 2 ++
> OvmfPkg/XenPlatformPei/XenPlatformPei.inf | 2 ++
> OvmfPkg/Library/LockBoxLib/LockBoxDxe.c | 4 +---
> .../Library/PlatformBootManagerLib/BdsPlatform.c | 2 +-
> OvmfPkg/SmmControl2Dxe/SmmControl2Dxe.c | 4 +---
> OvmfPkg/XenPlatformPei/Platform.c | 13 +++++++++++++
> 8 files changed, 22 insertions(+), 9 deletions(-)
>
> --
> 2.31.1
>
>
>
>
>
>
prev parent reply other threads:[~2021-08-31 11:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 1:31 [RESEND PATCH v3 0/4] Fix OvmfXen boot failure due to s3 support state Lin, Gary (HPS OE-Linux)
2021-08-31 1:31 ` [RESEND PATCH v3 1/4] OvmfPkg/OvmfXen: set PcdAcpiS3Enable at initialization Lin, Gary (HPS OE-Linux)
2021-08-31 1:31 ` [RESEND PATCH v3 2/4] OvmfPkg/LockBoxLib: use PcdAcpiS3Enable to detect S3 support Lin, Gary (HPS OE-Linux)
2021-08-31 1:31 ` [RESEND PATCH v3 3/4] OvmfPkg/PlatformBootManagerLib: " Lin, Gary (HPS OE-Linux)
2021-08-31 1:31 ` [RESEND PATCH v3 4/4] OvmfPkg/SmmControl2Dxe: " Lin, Gary (HPS OE-Linux)
2021-08-31 11:08 ` Ard Biesheuvel [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='CAMj1kXHUHt=0+L7=ToY-WW1a7WgXeFisqn6oZHVjFuSUegLrvA@mail.gmail.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