From: "Brijesh Singh" <brijesh.singh@amd.com>
To: devel@edk2.groups.io, kraxel@redhat.com, Min Xu <min.m.xu@intel.com>
Cc: brijesh.singh@amd.com, Ard Biesheuvel <ardb+tianocore@kernel.org>,
Jordan Justen <jordan.l.justen@intel.com>,
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: [edk2-devel] [PATCH V9 3/4] OvmfPkg: Add IntelTdxMetadata.asm
Date: Wed, 13 Oct 2021 06:44:28 -0500 [thread overview]
Message-ID: <e9f048ca-a0ec-0bba-3903-59a39790a6be@amd.com> (raw)
In-Reply-To: <20211012072228.h3meki5hmw27fn32@sirius.home.kraxel.org>
On 10/12/21 12:22 AM, Gerd Hoffmann via groups.io wrote:
> Hi,
>
>> +; - Type field means this section is of BFV. This field is designed for the
>> +; purpose that in some case host VMM may do some additional processing based
>> +; upon the section type. TdHob section is an example. Host VMM pass the
>> +; physical memory information to the guest firmware by writing the data in
>> +; the memory region designated by TdHob section.
> Brijesh? What are your plans? Do you want use this too?
Based on the previous comment by Jiewen it seems TDX folks want to have
a separate metadata for flexibility. In the v9, I am creating metadata
just for the SEV with a different GUID. Basically same as version 8 but
now the number of descriptors will be smaller (since we focus on SEV-SNP).
thanks
> If so, then the section types need some more structure. I think best
> would be reserve blocks, something like 0x00 -> 0xff common types (bfv,
> cfv, temp_mem), 0x100 -> 0x1ff tdx (td_hob), 0x200 -> 0x2ff sev (cpuid,
> secrets, ...).
>
> take care,
> Gerd
>
>
>
>
>
>
next prev parent reply other threads:[~2021-10-13 11:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-12 2:37 [PATCH V9 0/4] Add Intel TDX support in OvmfPkg/ResetVector Min Xu
2021-10-12 2:37 ` [PATCH V9 1/4] OvmfPkg: Copy Main.asm from UefiCpuPkg to OvmfPkg's ResetVector Min Xu
2021-10-12 7:02 ` Gerd Hoffmann
2021-10-13 0:39 ` Min Xu
2021-10-12 2:37 ` [PATCH V9 2/4] OvmfPkg: Clear WORK_AREA_GUEST_TYPE in Main.asm Min Xu
2021-10-12 7:02 ` Gerd Hoffmann
2021-10-12 13:22 ` Lendacky, Thomas
2021-10-13 0:58 ` [edk2-devel] " Min Xu
2021-10-13 15:45 ` Brijesh Singh
2021-10-14 1:50 ` Min Xu
2021-10-12 2:37 ` [PATCH V9 3/4] OvmfPkg: Add IntelTdxMetadata.asm Min Xu
2021-10-12 7:22 ` Gerd Hoffmann
2021-10-13 11:44 ` Brijesh Singh [this message]
2021-10-13 13:07 ` [edk2-devel] " Gerd Hoffmann
2021-10-12 2:37 ` [PATCH V9 4/4] OvmfPkg: Enable TDX in ResetVector Min Xu
2021-10-12 7:43 ` Gerd Hoffmann
2021-10-13 5:16 ` [edk2-devel] " 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=e9f048ca-a0ec-0bba-3903-59a39790a6be@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