;\r
guidedStructureStart:\r
\r
+%ifdef ARCH_X64\r
;\r
+; TDX Metadata offset block\r
+;\r
+; TdxMetadata.asm is included in ARCH_X64 because Inte TDX is only\r
+; available in ARCH_X64. Below block describes the offset of\r
+; TdxMetadata block in Ovmf image\r
+;\r
+; GUID : e47a6535-984a-4798-865e-4685a7bf8ec2\r
+;\r
+tdxMetadataOffsetStart:\r
+ DD fourGigabytes - TdxMetadataGuid - 16\r
+ DW tdxMetadataOffsetEnd - tdxMetadataOffsetStart\r
+ DB 0x35, 0x65, 0x7a, 0xe4, 0x4a, 0x98, 0x98, 0x47\r
+ DB 0x86, 0x5e, 0x46, 0x85, 0xa7, 0xbf, 0x8e, 0xc2\r
+tdxMetadataOffsetEnd:\r
+\r
+%endif\r
+\r
+; SEV Hash Table Block\r
+;\r
+; This describes the guest ram area where the hypervisor should\r
+; install a table describing the hashes of certain firmware configuration\r
+; device files that would otherwise be passed in unchecked. The current\r
+; use is for the kernel, initrd and command line values, but others may be\r
+; added. The data format is:\r
+;\r
+; base physical address (32 bit word)\r
+; table length (32 bit word)\r
+;\r
+; GUID (SEV FW config hash block): 7255371f-3a3b-4b04-927b-1da6efa8d454\r
+;\r
+sevFwHashBlockStart:\r
+ DD SEV_FW_HASH_BLOCK_BASE\r
+ DD SEV_FW_HASH_BLOCK_SIZE\r
+ DW sevFwHashBlockEnd - sevFwHashBlockStart\r
+ DB 0x1f, 0x37, 0x55, 0x72, 0x3b, 0x3a, 0x04, 0x4b\r
+ DB 0x92, 0x7b, 0x1d, 0xa6, 0xef, 0xa8, 0xd4, 0x54\r
+sevFwHashBlockEnd:\r
+\r
; SEV Secret block\r
;\r
; This describes the guest ram area where the hypervisor should\r