From: "Bret Barkelew" <bret.barkelew@microsoft.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
Arti Gupta <argu@microsoft.com>
Subject: ArmPkg: TranslationTable exceeding TempRam on virtual systems
Date: Thu, 27 May 2021 23:28:54 +0000 [thread overview]
Message-ID: <MW4PR21MB1907E1CC4E3D21E811372B05EF239@MW4PR21MB1907.namprd21.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 560 bytes --]
I’m fielding a series of questions coming out of our compatriot team that deals with virtual FW (for HyperV). They’re seeing ARM64 systems that have lots of RAM vastly exceeding the TempRam that’s passed into the system due to HOB allocations to create all the 4k entries for the early page tables.
Is this a known limitation or are we doing something dumb?
Is there a way to sparsely populate the page tables and fill them in more in DXE?
I’ve seen some questions about 64k pages on the list before. Is that an option?
Thanks in advance!
- Bret
[-- Attachment #2: Type: text/html, Size: 2010 bytes --]
next reply other threads:[~2021-05-27 23:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-27 23:28 Bret Barkelew [this message]
2021-07-01 9:35 ` ArmPkg: TranslationTable exceeding TempRam on virtual systems Arti Gupta
2021-07-29 5:23 ` Arti Gupta
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=MW4PR21MB1907E1CC4E3D21E811372B05EF239@MW4PR21MB1907.namprd21.prod.outlook.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