From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, kraxel@redhat.com
Cc: Oliver Steffen <osteffen@redhat.com>,
Ard Biesheuvel <ardb+tianocore@kernel.org>,
Jiewen Yao <jiewen.yao@intel.com>
Subject: Re: [edk2-devel] [PATCH v3 4/4] OvmfPkg/PlatformPei: log pei memory cap details
Date: Thu, 15 Feb 2024 09:24:41 +0100 [thread overview]
Message-ID: <75e394af-7538-91fc-4788-e6c8b25ca2be@redhat.com> (raw)
In-Reply-To: <20240214104504.2931339-5-kraxel@redhat.com>
On 2/14/24 11:45, Gerd Hoffmann wrote:
> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
> ---
> OvmfPkg/PlatformPei/MemDetect.c | 24 ++++++++++++++++++++++++
> 1 file changed, 24 insertions(+)
>
> diff --git a/OvmfPkg/PlatformPei/MemDetect.c b/OvmfPkg/PlatformPei/MemDetect.c
> index 81c29c626bb3..04409b28bacf 100644
> --- a/OvmfPkg/PlatformPei/MemDetect.c
> +++ b/OvmfPkg/PlatformPei/MemDetect.c
> @@ -263,6 +263,30 @@ GetPeiMemoryCap (
> //
> MemoryCap = EFI_PAGES_TO_SIZE ((UINTN)TotalPages) + ApStacks + SIZE_64MB;
>
> + DEBUG ((
> + DEBUG_INFO,
> + "%a: page tables: %6lu KB (%u/%u/%u/%u pages for levels 5/4/3/2)\n",
> + __func__,
> + RShiftU64 (EFI_PAGES_TO_SIZE ((UINTN)TotalPages), 10),
> + Level5Pages,
> + Level4Pages,
> + Level3Pages,
> + Level2Pages
> + ));
> + DEBUG ((
> + DEBUG_INFO,
> + "%a: ap stacks: %6lu KB (%u cpus)\n",
> + __func__,
> + RShiftU64 (ApStacks, 10),
> + PlatformInfoHob->PcdCpuMaxLogicalProcessorNumber
> + ));
> + DEBUG ((
> + DEBUG_INFO,
> + "%a: memory cap: %6lu KB\n",
> + __func__,
> + RShiftU64 (MemoryCap, 10)
> + ));
> +
> ASSERT (MemoryCap <= MAX_UINT32);
> return (UINT32)MemoryCap;
> }
Reviewed-by: Laszlo Ersek <lersek@redhat.com>
This series is now ready for merging, as far as I'm concerned (thanks
for the updates in the other patches too, I've re-checked them). Please
send a reminder after the stable tag.
Thanks!
Laszlo
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#115492): https://edk2.groups.io/g/devel/message/115492
Mute This Topic: https://groups.io/mt/104350494/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2024-02-15 8:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 10:45 [edk2-devel] [PATCH v3 0/4] OvmfPkg/PlatformPei: scaleability fixes for GetPeiMemoryCap() Gerd Hoffmann
2024-02-14 10:45 ` [edk2-devel] [PATCH v3 1/4] OvmfPkg/PlatformPei: log a warning when memory is tight Gerd Hoffmann
2024-02-14 10:45 ` [edk2-devel] [PATCH v3 2/4] OvmfPkg/PlatformPei: consider AP stacks for pei memory cap Gerd Hoffmann
2024-02-14 10:45 ` [edk2-devel] [PATCH v3 3/4] OvmfPkg/PlatformPei: rewrite page table calculation Gerd Hoffmann
2024-02-14 10:45 ` [edk2-devel] [PATCH v3 4/4] OvmfPkg/PlatformPei: log pei memory cap details Gerd Hoffmann
2024-02-15 8:24 ` Laszlo Ersek [this message]
2024-02-27 8:44 ` Gerd Hoffmann
2024-02-27 13:33 ` 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=75e394af-7538-91fc-4788-e6c8b25ca2be@redhat.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