Fix to resolve the OS boot issue when booting on WilsonCitySMT board. ASSERT_EFI_ERROR(StatusParameter) needs to be passed with Error Status code and not with TRUE or FALSE. Replaced ASSERT_EFI_ERROR

PlatformPei detects all the guest memory and marks it as a SYSTEM_RAM unless its an MMIO or added as reserved in e820 map file. Since the Secrets and CPUID pages are part of system RAM so we need to

At least in the current Ovmf implementation the PlatformPei must initialize some of the PCDs used by the MpLibInit such as PcdCpuBootLogicalProcessorNumber and other AP related PCD. PlatformPei uses

Hi, I'm going to drop this from the v2 of this set because while the mainline patch has a bunch of Ack's, its stuck because we are still discussing whether a DSD here is the right choice.

Hi, Its a bit late, but this looks fine. THanks!

Yes, I think that will work. For SEV case so far there was no need for to move in MdePkg so I kept in UefiCpuPkg but I am good with moving.

Yes, this should go away with Lazy validation. Ah, my bad I missed your request to document it. I will add the comment.

I don't see a strong reason t move over unless someone else sees a real need for it. We anyway have to maintain the backward compatibility because older qemu will look for those region through other

Currently, the flag "-fpie" is passed for all builds with a GCC family toolchain, including CLANGPDB. CLANGPDB however does not support this flag as it generates PE/COFF files directly. As the flag

V2: Update patch to account for ARM support Currently, the flag "-fpie" is passed for all builds with a GCC family toolchain, including CLANGPDB. CLANGPDB however does not support this flag as it

The commit 80e67af9afca added support for the generic work area concept used mainly by the encrypted VMs but missed update the AmdSev package. Fixes: 80e67af9afca ("OvmfPkg: introduce a common work

The commit 80e67af9afca added support for the generic work area concept used mainly by the encrypted VMs. In the past, the work area was preliminary used by the SEV-ES VMs. The SEV-ES support is

We missed updating the AmdSev package and Ia32 buid to use new work area. Brijesh Singh (2): Ovmfpkg: update Ia32 build to use new work area OvmfPkg/AmdSev: update the fdf to use new workarea

Hi Abner, This patch: https://edk2.groups.io/g/devel/message/81310 renames: gArmTokenSpaceGuid.PcdPciMmio32Translation to: gEfiMdePkgTokenSpaceGuid.PcdPciMmio32Translation but

It looks like all errors are still related to ECC and PatchCheck, even though I'm just matching the rest of the file. Please advise if we want to update the entire file.

Hi Sami To clarify my description: I am OK to define it in an architecture neutral protocol, such as EFI_TEE_MEASUREMENT_PROTOCOL, or EFI_CCAM_PROTOCOL. I am happy to do that. However, at current

Marvin, It's fine to use your below patch to fix this issue. Please help to check-in

Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=3599 Signed-off-by: Gerd Hoffmann <kraxel@...> Acked-by: Jiewen Yao <Jiewen.yao@...> --- OvmfPkg/Microvm/README | 50

Add virtio-mmio support (VirtioMmioDeviceLib and VirtioFdtDxe). https://bugzilla.tianocore.org/show_bug.cgi?id=3689 Signed-off-by: Gerd Hoffmann <kraxel@...> ---

FdtClient is unhappy without a device tree, so add an empty fdt which we can use in case etc/fdt is not present in fw_cfg. https://bugzilla.tianocore.org/show_bug.cgi?id=3689 Signed-off-by: Gerd