Add BhyvePkg, to support the bhyve hypervisor
BhyvePkg supports the bhyve hypervisor, which is a hypervisor/virtual machine manager available on FreeBSD, macOS and Illumos. Signed-off-by: Rebecca Cran <rebecca@bsdio.com> Message-Id: <20200713054131.479627-2-rebecca@bsdio.com> Acked-by: Laszlo Ersek <lersek@redhat.com>
This commit is contained in:
committed by
mergify[bot]
parent
137c2c6eff
commit
656419f922
94
OvmfPkg/Bhyve/PlatformPei/Fv.c
Normal file
94
OvmfPkg/Bhyve/PlatformPei/Fv.c
Normal file
@@ -0,0 +1,94 @@
|
||||
/** @file
|
||||
Build FV related hobs for platform.
|
||||
|
||||
Copyright (c) 2006 - 2013, Intel Corporation. All rights reserved.<BR>
|
||||
SPDX-License-Identifier: BSD-2-Clause-Patent
|
||||
|
||||
**/
|
||||
|
||||
#include "PiPei.h"
|
||||
#include "Platform.h"
|
||||
#include <Library/DebugLib.h>
|
||||
#include <Library/HobLib.h>
|
||||
#include <Library/PeiServicesLib.h>
|
||||
#include <Library/PcdLib.h>
|
||||
|
||||
|
||||
/**
|
||||
Publish PEI & DXE (Decompressed) Memory based FVs to let PEI
|
||||
and DXE know about them.
|
||||
|
||||
@retval EFI_SUCCESS Platform PEI FVs were initialized successfully.
|
||||
|
||||
**/
|
||||
EFI_STATUS
|
||||
PeiFvInitialization (
|
||||
VOID
|
||||
)
|
||||
{
|
||||
BOOLEAN SecureS3Needed;
|
||||
|
||||
DEBUG ((DEBUG_INFO, "Platform PEI Firmware Volume Initialization\n"));
|
||||
|
||||
//
|
||||
// Create a memory allocation HOB for the PEI FV.
|
||||
//
|
||||
// Allocate as ACPI NVS is S3 is supported
|
||||
//
|
||||
BuildMemoryAllocationHob (
|
||||
PcdGet32 (PcdOvmfPeiMemFvBase),
|
||||
PcdGet32 (PcdOvmfPeiMemFvSize),
|
||||
mS3Supported ? EfiACPIMemoryNVS : EfiBootServicesData
|
||||
);
|
||||
|
||||
//
|
||||
// Let DXE know about the DXE FV
|
||||
//
|
||||
BuildFvHob (PcdGet32 (PcdOvmfDxeMemFvBase), PcdGet32 (PcdOvmfDxeMemFvSize));
|
||||
|
||||
SecureS3Needed = mS3Supported && FeaturePcdGet (PcdSmmSmramRequire);
|
||||
|
||||
//
|
||||
// Create a memory allocation HOB for the DXE FV.
|
||||
//
|
||||
// If "secure" S3 is needed, then SEC will decompress both PEI and DXE
|
||||
// firmware volumes at S3 resume too, hence we need to keep away the OS from
|
||||
// DXEFV as well. Otherwise we only need to keep away DXE itself from the
|
||||
// DXEFV area.
|
||||
//
|
||||
BuildMemoryAllocationHob (
|
||||
PcdGet32 (PcdOvmfDxeMemFvBase),
|
||||
PcdGet32 (PcdOvmfDxeMemFvSize),
|
||||
SecureS3Needed ? EfiACPIMemoryNVS : EfiBootServicesData
|
||||
);
|
||||
|
||||
//
|
||||
// Additionally, said decompression will use temporary memory above the end
|
||||
// of DXEFV, so let's keep away the OS from there too.
|
||||
//
|
||||
if (SecureS3Needed) {
|
||||
UINT32 DxeMemFvEnd;
|
||||
|
||||
DxeMemFvEnd = PcdGet32 (PcdOvmfDxeMemFvBase) +
|
||||
PcdGet32 (PcdOvmfDxeMemFvSize);
|
||||
BuildMemoryAllocationHob (
|
||||
DxeMemFvEnd,
|
||||
PcdGet32 (PcdOvmfDecompressionScratchEnd) - DxeMemFvEnd,
|
||||
EfiACPIMemoryNVS
|
||||
);
|
||||
}
|
||||
|
||||
//
|
||||
// Let PEI know about the DXE FV so it can find the DXE Core
|
||||
//
|
||||
PeiServicesInstallFvInfoPpi (
|
||||
NULL,
|
||||
(VOID *)(UINTN) PcdGet32 (PcdOvmfDxeMemFvBase),
|
||||
PcdGet32 (PcdOvmfDxeMemFvSize),
|
||||
NULL,
|
||||
NULL
|
||||
);
|
||||
|
||||
return EFI_SUCCESS;
|
||||
}
|
||||
|
Reference in New Issue
Block a user