e23f8f52fd
RFC: https://bugzilla.tianocore.org/show_bug.cgi?id=3429 There are below changes in PlatformInitLib for Tdx guest: 1. Publish ram regions In Tdx guest, the system memory is passed in TdHob by host VMM. So the major task of PlatformTdxPublishRamRegions is to walk thru the TdHob list and transfer the ResourceDescriptorHob and MemoryAllocationHob to the hobs in DXE phase. 2. Build MemoryAllocationHob for Tdx Mailbox and Ovmf work area. 3. Update of PlatformAddressWidthInitialization. The physical address width that Tdx guest supports is either 48 or 52. 4. Update of PlatformMemMapInitialization. 0xA0000 - 0xFFFFF is VGA bios region. Platform initialization marks the region as MMIO region. Dxe code maps MMIO region as IO region. As TDX guest, MMIO region is maps as shared. However VGA BIOS doesn't need to be shared. Guest TDX Linux maps VGA BIOS as private and accesses for BIOS and stuck on repeating EPT violation. VGA BIOS (more generally ROM region) should be private. Skip marking VGA BIOA region [0xa000, 0xfffff] as MMIO in HOB. Cc: Ard Biesheuvel <ardb+tianocore@kernel.org> Cc: Jordan Justen <jordan.l.justen@intel.com> Cc: Brijesh Singh <brijesh.singh@amd.com> Cc: Erdem Aktas <erdemaktas@google.com> Cc: James Bottomley <jejb@linux.ibm.com> Cc: Jiewen Yao <jiewen.yao@intel.com> Cc: Tom Lendacky <thomas.lendacky@amd.com> Cc: Gerd Hoffmann <kraxel@redhat.com> Acked-by: Gerd Hoffmann <kraxel@redhat.com> Reviewed-by: Jiewen Yao <jiewen.yao@intel.com> Signed-off-by: Min Xu <min.m.xu@intel.com>
47 lines
1.1 KiB
C
47 lines
1.1 KiB
C
/** @file
|
|
Initialize Intel TDX support.
|
|
|
|
Copyright (c) 2021, Intel Corporation. All rights reserved.<BR>
|
|
|
|
SPDX-License-Identifier: BSD-2-Clause-Patent
|
|
|
|
**/
|
|
|
|
#include <PiPei.h>
|
|
|
|
/**
|
|
In Tdx guest, some information need to be passed from host VMM to guest
|
|
firmware. For example, the memory resource, etc. These information are
|
|
prepared by host VMM and put in HobList which is described in TdxMetadata.
|
|
|
|
Information in HobList is treated as external input. From the security
|
|
perspective before it is consumed, it should be validated.
|
|
|
|
@retval EFI_SUCCESS Successfully process the hoblist
|
|
@retval Others Other error as indicated
|
|
**/
|
|
EFI_STATUS
|
|
EFIAPI
|
|
ProcessTdxHobList (
|
|
VOID
|
|
)
|
|
{
|
|
return EFI_UNSUPPORTED;
|
|
}
|
|
|
|
/**
|
|
In Tdx guest, the system memory is passed in TdHob by host VMM. So
|
|
the major task of PlatformTdxPublishRamRegions is to walk thru the
|
|
TdHob list and transfer the ResourceDescriptorHob and MemoryAllocationHob
|
|
to the hobs in DXE phase.
|
|
|
|
MemoryAllocationHob should also be created for Mailbox and Ovmf work area.
|
|
**/
|
|
VOID
|
|
EFIAPI
|
|
PlatformTdxPublishRamRegions (
|
|
VOID
|
|
)
|
|
{
|
|
}
|