From: "Lendacky, Thomas" <thomas.lendacky@amd.com>
To: "Xu, Min M" <min.m.xu@intel.com>, Gerd Hoffmann <kraxel@redhat.com>
Cc: joeyli <jlee@suse.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
"Aktas, Erdem" <erdemaktas@google.com>,
James Bottomley <jejb@linux.ibm.com>,
"Yao, Jiewen" <jiewen.yao@intel.com>,
Michael Roth <michael.roth@amd.com>
Subject: Re: [PATCH V1 1/1] OvmfPkg/PlatformPei: Skip PlatformInitEmuVariableNvStore in SEV guest
Date: Thu, 6 Apr 2023 15:28:32 -0500 [thread overview]
Message-ID: <5d170680-0a9e-2d5f-ecc1-e9f587548e3c@amd.com> (raw)
In-Reply-To: <PH0PR11MB5064B1575F38459DE8989675C5919@PH0PR11MB5064.namprd11.prod.outlook.com>
On 4/5/23 20:42, Xu, Min M wrote:
> On April 3, 2023 7:21 PM, Gerd Hoffmann wrote:
>>>> I agree that the efi variable store is not secure without smm. But
>>>> after 58eb8517ad7b be introduced, the -D SECURE_BOOT_ENABLE doesn't
>>>> work with SEV. System just hangs in "NvVarStore FV headers were invalid."
>>> Hi, Joeyli
>>> ASSERT is triggered in DEBUG version. In RELEASE version ASSERT is skipped
>> and an error code is returned. So system will not hang.
>>> So another solution is simply remove the ASSERT. Then an error message is
>> dumped out and system continues.
>>>
>>> @Gerd Hoffmann @Tom Lendacky @joeyli What's your thought?
>>
>> Maybe we just need to call ReserveEmuVariableNvStore a bit later?
>>
> I think we can still call ReserveEmuVariableNvStore at PEI phase, but move the initialization of EmuVariableNvStore to https://github.com/tianocore/edk2/blob/master/OvmfPkg/EmuVariableFvbRuntimeDxe/Fvb.c#L780-L783
> @Tom Lendacky At this moment, is SEV guest available to read the content from VarStore?
It's quite possible. If you can work up a quick patch, I'll test it out.
Thanks,
Tom
>
> Thanks
> Min
next prev parent reply other threads:[~2023-04-06 20:28 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 5:23 [PATCH V1 1/1] OvmfPkg/PlatformPei: Skip PlatformInitEmuVariableNvStore in SEV guest Min Xu
2023-03-30 7:50 ` Gerd Hoffmann
2023-03-31 7:59 ` joeyli
2023-03-31 8:25 ` Gerd Hoffmann
2023-03-31 14:48 ` joeyli
2023-04-03 0:21 ` Min Xu
2023-04-03 11:20 ` Gerd Hoffmann
2023-04-06 1:42 ` Min Xu
2023-04-06 20:28 ` Lendacky, Thomas [this message]
2023-04-07 1:56 ` Min Xu
2023-04-07 14:49 ` [edk2-devel] " joeyli
2023-04-07 17:00 ` Lendacky, Thomas
2023-04-11 10:04 ` Gerd Hoffmann
2023-04-11 18:03 ` Lendacky, Thomas
2023-04-12 7:24 ` Gerd Hoffmann
2023-04-12 15:23 ` Lendacky, Thomas
2023-04-13 6:05 ` Gerd Hoffmann
2023-04-13 13:58 ` Lendacky, Thomas
2023-04-14 10:20 ` Gerd Hoffmann
2023-04-20 15:16 ` Lendacky, Thomas
2023-04-21 9:18 ` Gerd Hoffmann
2023-04-21 20:49 ` Lendacky, Thomas
2023-04-24 9:45 ` Gerd Hoffmann
2023-04-26 20:43 ` Lendacky, Thomas
2023-04-28 8:41 ` Gerd Hoffmann
2023-05-01 19:06 ` Lendacky, Thomas
2023-04-07 9:41 ` joeyli
2023-04-07 11:54 ` Min Xu
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=5d170680-0a9e-2d5f-ecc1-e9f587548e3c@amd.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