Hi Pedro,

Current memory protection settings rely on FixedAtBuild PCD values (minus PcdSetNxForStack). Because of this, the memory protection configuration interface is fixed in nature. Cases arise in which

In the case where the root bridge's Mem.Limit is the base address of PCIe MMIO, subtract one to make a valid end address. This fixes an issue where CpuDxe returns "Length(0x50000001) is not aligned!"

TDX_WORK_AREA is piece of TdxMailbox which is located in the MEMFD started from PcdOvmfSecGhcbBackupBase. In Td guest, this memory region is initialized to all-0 by host VMM. In legacy guests, I am

According to the logs, the .raw file binaries were committed 10 years ago. This commit in 2014 make a change to how the build defines are processed. It also switches from using ASM to NASM for the

Hi., Michael Even If we generate the binaries using the Python2 also, it's getting changed. Can you confirm from your end by generating the binaries using the build.py in Python2 Regards, Ashraf

Is the memory area guaranteed to be zeroed for legacy guests? Hopefully, this won't trip up a non-TDX guest with a false match (highly unlikely, though). If you clear ebx here... ... you can remove

Hi. Ray Based on Dov Murik <dovmurik@...> Comments to take the python script changes separately, I have filed the Bugzilla for that

Hi Andrew, Marvin, RE: The package name: It doesn't sound like a bad idea to have something like a FileSystemPkg and have a bunch of different filesystems inside of it, but I'll defer to you and my

Hi Ashraf, Why would an update to the Python script to Python3 cause any changes to the binary images the script produces. If they are different, then that would seem to imply that the change

[edk2-devel] [PATCH] REF:https://bugzilla.tianocore.org/show_bug.cgi?id=3506 Build Scrips for Reset Vector currently based on Python 2 which is already EOL, needs to modify the build script based

Great idea, maybe it could be added to that wiki list of topic suggestions (preferably close to the top)? :) Best regards, Marvin

Marvin, Good point that the FatPkg was more about license boundary than anything else, so I’m not opposed to a more generic package name. I think having a default PCD option of read only is a good

"Mapping" implies that the MMU is on, but this code boots with the MMU off. Unlike x86, ARM does not define any physical address ranges that are guaranteed to be backed by DRAM, so a portable image

Reviewed-by: Nickle Wang <nickle.wang@...> Thanks, Nickle

Reviewed-by: Nickle Wang <nickle.wang@...> Thanks, Nickle

Reviewed-by: Nickle Wang <nickle.wang@...> Thanks, Nickle

Expanding audience to the full dev list… See below… - Bret

Here is the documentation: https://github.com/osresearch/kexec-load/blob/main/README.md