From: "Ard Biesheuvel" <ardb@kernel.org>
To: edk2-devel-groups-io <devel@edk2.groups.io>, annie.li@oracle.com
Cc: Ard Biesheuvel <ardb+tianocore@kernel.org>,
Jiewen Yao <jiewen.yao@intel.com>,
Jordan Justen <jordan.l.justen@intel.com>,
"kraxel@redhat.com >> Gerd Hoffmann" <kraxel@redhat.com>,
Karl Franz Heubaum <karl.heubaum@oracle.com>,
Aaron Young <aaron.young@oracle.com>
Subject: Re: [edk2-devel] [PATCH V2 1/1] OvmfPkg/OvmfPkg*.dsc: Increase ACPI Reclaim memory size
Date: Tue, 3 May 2022 18:25:58 +0200 [thread overview]
Message-ID: <CAMj1kXEnQrBUKOXPRybKm1Rj=7BXFZ0vd2GyHJMc+Rqh6v_3XA@mail.gmail.com> (raw)
In-Reply-To: <c1e52c43-87b4-035c-02cc-7214f5de1fd7@oracle.com>
On Tue, 3 May 2022 at 17:54, annie li <annie.li@oracle.com> wrote:
>
> Adding maintainers into the CC list...
>
> On 5/2/2022 5:05 PM, annie li wrote:
> > Hello
> >
> > I am wondering if anyone will review this patch please? Any comments
> > are welcome.
> >
> > Thanks
> >
> > Annie
> >
> > On 4/15/2022 5:15 PM, annie li wrote:
> >> The current ACPI Reclaim memory size is set as 0x10(64k). The
> >> ACPI table size will be increased if the memory slots' number of
> >> the guest gets increased. In the guest with more memory slots,
> >> the ACPI Reclaim memory size may not be sufficient for hibernation.
> >> This may cause resume failure of the hibernated guest that was
> >> booted up with a fresh copied writable OVMF_VARS file. However,
> >> the failure doesn't happen in following hibernation/resume
> >> cycles.
> >>
> >> The ACPI_MAX_RAM_SLOTS is set as 256 in the current QEMU. With
> >> ACPI_MAX_RAM_SLOTS, 18 pages are required to be allocated in ACPI
> >> Reclaim memory. However, due to the 0x10(16 pages) setting, 2 extra
> >> pages will be allocated in other space. This may break the
> >> hibernation/resume in the above scenario.
> >>
> >> This patch increases the ACPI Reclaim memory size to 0x12, i.e.
> >> PcdMemoryTypeEfiACPIReclaimMemory is set as 0x12(18 pages).
> >>
> >> Signed-off-by: Annie Li <annie.li@oracle.com>
> >> ---
> >> OvmfPkg/OvmfPkgIa32.dsc | 2 +-
> >> OvmfPkg/OvmfPkgIa32X64.dsc | 2 +-
> >> OvmfPkg/OvmfPkgX64.dsc | 2 +-
> >> 3 files changed, 3 insertions(+), 3 deletions(-)
> >>
No objections from me but before merging this, I'll give the other
folks the opportunity to chime in as well.
> >> diff --git a/OvmfPkg/OvmfPkgIa32.dsc b/OvmfPkg/OvmfPkgIa32.dsc
> >> index 29eea82571..fb158f98c9 100644
> >> --- a/OvmfPkg/OvmfPkgIa32.dsc
> >> +++ b/OvmfPkg/OvmfPkgIa32.dsc
> >> @@ -547,7 +547,7 @@
> >> # unknown) workloads / boot paths.
> >>
> >> #
> >>
> >> gEmbeddedTokenSpaceGuid.PcdMemoryTypeEfiACPIMemoryNVS|0x80
> >>
> >> - gEmbeddedTokenSpaceGuid.PcdMemoryTypeEfiACPIReclaimMemory|0x10
> >>
> >> + gEmbeddedTokenSpaceGuid.PcdMemoryTypeEfiACPIReclaimMemory|0x12
> >>
> >> gEmbeddedTokenSpaceGuid.PcdMemoryTypeEfiReservedMemoryType|0x80
> >>
> >> gEmbeddedTokenSpaceGuid.PcdMemoryTypeEfiRuntimeServicesCode|0x100
> >>
> >> gEmbeddedTokenSpaceGuid.PcdMemoryTypeEfiRuntimeServicesData|0x100
> >>
> >> diff --git a/OvmfPkg/OvmfPkgIa32X64.dsc b/OvmfPkg/OvmfPkgIa32X64.dsc
> >> index 56d3c49ab2..30d47ca28a 100644
> >> --- a/OvmfPkg/OvmfPkgIa32X64.dsc
> >> +++ b/OvmfPkg/OvmfPkgIa32X64.dsc
> >> @@ -552,7 +552,7 @@
> >> # unknown) workloads / boot paths.
> >>
> >> #
> >>
> >> gEmbeddedTokenSpaceGuid.PcdMemoryTypeEfiACPIMemoryNVS|0x80
> >>
> >> - gEmbeddedTokenSpaceGuid.PcdMemoryTypeEfiACPIReclaimMemory|0x10
> >>
> >> + gEmbeddedTokenSpaceGuid.PcdMemoryTypeEfiACPIReclaimMemory|0x12
> >>
> >> gEmbeddedTokenSpaceGuid.PcdMemoryTypeEfiReservedMemoryType|0x80
> >>
> >> gEmbeddedTokenSpaceGuid.PcdMemoryTypeEfiRuntimeServicesCode|0x100
> >>
> >> gEmbeddedTokenSpaceGuid.PcdMemoryTypeEfiRuntimeServicesData|0x100
> >>
> >> diff --git a/OvmfPkg/OvmfPkgX64.dsc b/OvmfPkg/OvmfPkgX64.dsc
> >> index f0924c0f9d..6c10ceedd7 100644
> >> --- a/OvmfPkg/OvmfPkgX64.dsc
> >> +++ b/OvmfPkg/OvmfPkgX64.dsc
> >> @@ -552,7 +552,7 @@
> >> # unknown) workloads / boot paths.
> >>
> >> #
> >>
> >> gEmbeddedTokenSpaceGuid.PcdMemoryTypeEfiACPIMemoryNVS|0x80
> >>
> >> - gEmbeddedTokenSpaceGuid.PcdMemoryTypeEfiACPIReclaimMemory|0x10
> >>
> >> + gEmbeddedTokenSpaceGuid.PcdMemoryTypeEfiACPIReclaimMemory|0x12
> >>
> >> gEmbeddedTokenSpaceGuid.PcdMemoryTypeEfiReservedMemoryType|0x80
> >>
> >> gEmbeddedTokenSpaceGuid.PcdMemoryTypeEfiRuntimeServicesCode|0x100
> >>
> >> gEmbeddedTokenSpaceGuid.PcdMemoryTypeEfiRuntimeServicesData|0x100
> >>
> >
> >
> >
> >
> >
>
>
>
>
>
next prev parent reply other threads:[~2022-05-03 16:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <16E62E6A940424A8.9469@groups.io>
2022-05-02 21:05 ` [edk2-devel] [PATCH V2 1/1] OvmfPkg/OvmfPkg*.dsc: Increase ACPI Reclaim memory size annie li
[not found] ` <16EB65B9C6B20F3F.8534@groups.io>
2022-05-03 15:54 ` annie li
2022-05-03 16:25 ` Ard Biesheuvel [this message]
2022-05-13 11:28 ` annie li
2022-07-22 12:42 ` annie li
2022-09-06 16:56 ` Ard Biesheuvel
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='CAMj1kXEnQrBUKOXPRybKm1Rj=7BXFZ0vd2GyHJMc+Rqh6v_3XA@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