From: "Gerd Hoffmann" <kraxel@redhat.com>
To: Min Xu <min.m.xu@intel.com>
Cc: devel@edk2.groups.io, Erdem Aktas <erdemaktas@google.com>,
James Bottomley <jejb@linux.ibm.com>,
Jiewen Yao <jiewen.yao@intel.com>,
Tom Lendacky <thomas.lendacky@amd.com>
Subject: Re: [PATCH 3/3] OvmfPkg: Initialize NvVarStore with Configuration FV in Td guest
Date: Mon, 20 Jun 2022 13:01:24 +0200 [thread overview]
Message-ID: <20220620110124.s4sutzqnsvlmvdg5@sirius.home.kraxel.org> (raw)
In-Reply-To: <b0125a87568f6ab9ae681dcf806e910dd0c41fbd.1655518585.git.min.m.xu@intel.com>
> + UINT8 *CfvBase;
> + UINT32 CfvSize;
>
> DEBUG ((DEBUG_INFO, "EMU Variable FVB Started\n"));
>
> @@ -774,6 +776,23 @@ FvbInitialize (
>
> mEmuVarsFvb.BufferPtr = Ptr;
>
> + //
> + // In Tdx guest the VarNvStore content should be initialized by the Configuration FV (CFV).
> + // Integrity of the CFV has been validated by TdxValidateCfv (@PlatformInitLib)
> + //
> + if (TdIsEnabled ()) {
> + CfvBase = (UINT8 *)(UINTN)PcdGet32 (PcdCfvBase);
> + CfvSize = (UINT32)PcdGet32 (PcdCfvRawDataSize);
> +
> + if (CfvSize > mEmuVarsFvb.Size) {
> + DEBUG ((DEBUG_ERROR, "Size of CFV is larger than the EMU Variable FVB.\n"));
> + ASSERT (FALSE);
> + } else {
> + CopyMem (Ptr, CfvBase, CfvSize);
> + Initialize = FALSE;
> + }
> + }
There is PcdEmuVariableNvStoreReserved for that. How about just
copying the store to ram, then set PcdEmuVariableNvStoreReserved
to the location and let the existing logic handle it?
Also why limit this to tdx?
take care,
Gerd
next prev parent reply other threads:[~2022-06-20 11:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-18 2:32 [PATCH 0/3] Enable Secure-Boot in Tdx guest Min Xu
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 [this message]
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=20220620110124.s4sutzqnsvlmvdg5@sirius.home.kraxel.org \
--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