From: "Min Xu" <min.m.xu@intel.com>
To: devel@edk2.groups.io
Cc: Min Xu <min.m.xu@intel.com>, Erdem Aktas <erdemaktas@google.com>,
James Bottomley <jejb@linux.ibm.com>,
Jiewen Yao <jiewen.yao@intel.com>,
Gerd Hoffmann <kraxel@redhat.com>,
Tom Lendacky <thomas.lendacky@amd.com>
Subject: [PATCH 0/3] Enable Secure-Boot in Tdx guest
Date: Sat, 18 Jun 2022 10:32:00 +0800 [thread overview]
Message-ID: <cover.1655518585.git.min.m.xu@intel.com> (raw)
Secure-Boot related variables include the PK/KEK/DB/DBX and they are
stored in NvVarStore (OVMF_VARS.fd). But QEMU command option -pflash is
not supported in Tdx guest. So when Tdx guest is booted,
EmuVariableFvbRuntimeDxe driver is loaded and the NvVarStore is
initialized with empty content. This patch-set is to initialize the
NvVarStore with the content of Configuration FV (CFV).
Before the NvVarStore is initialized with the content of CFV, CFV's
integrity should be validated. So patch #1/2 are imported to do such
validation.
Code: https://github.com/mxu9/edk2/tree/secure-boot.v1
Cc: Erdem Aktas <erdemaktas@google.com>
Cc: James Bottomley <jejb@linux.ibm.com>
Cc: Jiewen Yao <jiewen.yao@intel.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>
Cc: Tom Lendacky <thomas.lendacky@amd.com>
Signed-off-by: Min Xu <min.m.xu@intel.com>
*** BLURB HERE ***
Min M Xu (3):
OvmfPkg: Move TdxValidateCfv from PeilessStartupLib to PlatformInitLib
OvmfPkg: Validate Cfv integrity in Tdx guest
OvmfPkg: Initialize NvVarStore with Configuration FV in Td guest
OvmfPkg/EmuVariableFvbRuntimeDxe/Fvb.c | 19 +++
OvmfPkg/EmuVariableFvbRuntimeDxe/Fvb.inf | 2 +
OvmfPkg/Include/Library/PlatformInitLib.h | 17 ++
OvmfPkg/Library/PeilessStartupLib/IntelTdx.c | 153 ------------------
.../PeilessStartupInternal.h | 17 --
OvmfPkg/Library/PlatformInitLib/IntelTdx.c | 153 ++++++++++++++++++
OvmfPkg/Sec/SecMain.c | 8 +
OvmfPkg/Sec/SecMain.inf | 2 +
8 files changed, 201 insertions(+), 170 deletions(-)
--
2.29.2.windows.2
next reply other threads:[~2022-06-18 2:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-18 2:32 Min Xu [this message]
2022-06-18 2:32 ` [PATCH 1/3] OvmfPkg: Move TdxValidateCfv from PeilessStartupLib to PlatformInitLib Min Xu
2022-06-18 2:32 ` [PATCH 2/3] OvmfPkg: Validate Cfv integrity in Tdx guest Min Xu
2022-06-18 2:32 ` [PATCH 3/3] OvmfPkg: Initialize NvVarStore with Configuration FV in Td guest Min Xu
2022-06-20 11:01 ` Gerd Hoffmann
2022-06-22 2:02 ` Min Xu
2022-06-22 7:01 ` Gerd Hoffmann
2022-06-22 8:14 ` Min Xu
2022-06-22 9:22 ` Gerd Hoffmann
2022-06-23 0:40 ` Min Xu
2022-06-23 7:23 ` Gerd Hoffmann
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=cover.1655518585.git.min.m.xu@intel.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