From: "Dionna Glaze" <dionnaglaze@google.com>
To: devel@edk2.groups.io
Cc: Dionna Glaze <dionnaglaze@google.com>
Subject: [PATCHv2 0/4] Add safe unaccepted memory behavior
Date: Fri, 23 Sep 2022 20:34:27 +0000 [thread overview]
Message-ID: <20220923203431.1428535-1-dionnaglaze@google.com> (raw)
These three patches build on the lazy-accept patch series
"Introduce Lazy-accept for Tdx guest"
by adding SEV-SNP support for the MemoryAccept protocol, and
importantly making eager memory acceptance the default behavior.
For unaccepted memory to be enabled, we must know that the booted image
supports the unaccepted memory type. We add a trivial protocol that sets
a dynamic Pcd to true when called in order for the booted image to
signal its support for unaccepted memory. This does not need to be an
OsIndications bit because it does not need to be persisted.
We use the Pcd to disable a new ExitBootServices notification that
accepts all unaccepted memory, removes the unaccepted memory entries in
the memory space map, and then add the same memory ranges back as
conventional memory.
All images that support unaccepted memory must now locate and call this
new ENABLE_UNACCEPTED_MEMORY_PROTOCOL.
Changes since v1:
- Added a patch to classify SEV-SNP memory above 4GB unaccepted.
- Fixed style problems in EfiMemoryAcceptProtocol implementation.
Dionna Glaze (4):
OvmfPkg: Realize EfiMemoryAcceptProtocol in AmdSevDxe
DxeMain accepts all memory at EBS if needed
MdeModulePkg: add EnableUnacceptedMemoryProtocol
OvmfPkg/PlatformPei: SEV-SNP make >=4GB unaccepted
MdeModulePkg/Core/Dxe/DxeMain.h | 32 +++++
MdeModulePkg/Core/Dxe/DxeMain.inf | 3 +
MdeModulePkg/Core/Dxe/DxeMain/DxeMain.c | 19 ++-
MdeModulePkg/Core/Dxe/Mem/Page.c | 122 ++++++++++++++++++
MdeModulePkg/MdeModulePkg.dec | 9 ++
MdeModulePkg/MdeModulePkg.uni | 6 +
OvmfPkg/AmdSev/AmdSevX64.dsc | 1 +
OvmfPkg/AmdSevDxe/AmdSevDxe.c | 34 +++++
OvmfPkg/AmdSevDxe/AmdSevDxe.inf | 3 +
OvmfPkg/Bhyve/BhyveX64.dsc | 2 +
OvmfPkg/CloudHv/CloudHvX64.dsc | 2 +
OvmfPkg/Include/Library/MemEncryptSevLib.h | 14 ++
OvmfPkg/IntelTdx/IntelTdxX64.dsc | 2 +
.../Ia32/MemEncryptSevLib.c | 17 +++
.../X64/DxeSnpSystemRamValidate.c | 35 +++++
.../X64/PeiSnpSystemRamValidate.c | 17 +++
.../X64/SecSnpSystemRamValidate.c | 18 +++
OvmfPkg/OvmfPkgIa32X64.dsc | 2 +
OvmfPkg/OvmfPkgX64.dsc | 2 +
OvmfPkg/OvmfXen.dsc | 2 +
OvmfPkg/PlatformPei/AmdSev.c | 4 +
21 files changed, 345 insertions(+), 1 deletion(-)
--
2.37.3.998.g577e59143f-goog
next reply other threads:[~2022-09-23 20:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 20:34 Dionna Glaze [this message]
2022-09-23 20:34 ` [PATCH 1/4] OvmfPkg: Realize EfiMemoryAcceptProtocol in AmdSevDxe Dionna Glaze
2022-09-23 21:30 ` Lendacky, Thomas
2022-09-26 15:56 ` Dionna Glaze
2022-09-26 18:14 ` [edk2-devel] " Rebecca Cran
2022-09-23 20:34 ` [PATCH 2/4] DxeMain accepts all memory at EBS if needed Dionna Glaze
2022-09-23 21:34 ` Lendacky, Thomas
2022-09-23 20:34 ` [PATCHv2 3/4] MdeModulePkg: add EnableUnacceptedMemoryProtocol Dionna Glaze
2022-09-23 20:34 ` [PATCHv2 4/4] OvmfPkg/PlatformPei: SEV-SNP make >=4GB unaccepted Dionna Glaze
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=20220923203431.1428535-1-dionnaglaze@google.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