From: Larry Cleeton <Larry.Cleeton@microsoft.com>
To: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: EFI_MEMORY_ATTRIBUTES_TABLE not in runtime memory
Date: Mon, 18 Sep 2017 19:48:36 +0000 [thread overview]
Message-ID: <DM5PR21MB0185BB85C95DFD308A81E360E1630@DM5PR21MB0185.namprd21.prod.outlook.com> (raw)
The EFI_MEMORY_ATTRIBUTES_TABLE constructed in MdeModulePkg/core/dxe/misc/MemoryAttributesTable.c is allocating the table memory using AllocatePool(). It seems it should be allocated using AllocateRuntimePool(). We've observed Linux kernels seeing a zeroed table, likely because those boot services memory pages have been reclaimed and zeroed. It appears that several other configuration tables are allocated with runtime memory. I haven't found any specific statements that this table should be in runtime memory. However it seems pragmatic and consistent that it be in runtime memory.
next reply other threads:[~2017-09-18 19:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-18 19:48 Larry Cleeton [this message]
2017-09-19 1:52 ` EFI_MEMORY_ATTRIBUTES_TABLE not in runtime memory Zeng, Star
2017-09-19 2:26 ` 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=DM5PR21MB0185BB85C95DFD308A81E360E1630@DM5PR21MB0185.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