I'd like to propose adding EFI_MP_SERVICES_PROTOCOL support for AARCH64 systems. I've attached two patches to implement support for it in the DXE phase, based on code in EmulatorPkg and UefiCpuPkg.

I would like to start a discussion regarding integration of the static analysis (SA) into the edk2 workflow. I assume the SA benefits are well understood, so I'll get straight to the point; however,

Hello Jiewen, Thanks for writing this up. As you know, ARM is a bit behind in the CCA space, and so I will not be able to take part in these discussions in great detail. I will leave it to the

Hi I would like to raise the topic on a confidential computing support in OVMF. The main target is AMD SEV feature and Intel TDX feature in OVMF package. The goal is to create a guidance for our

The EFI System Partition is defined to be FAT32 by the UEFI Spec for interoperability. It defines the file system drivers required for the firmware and OS. So changing that is not really an option.

Hi Pedro,

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

I think the Terminal driver may have some similar logic to convert UTF-8 terminals to/from the UEFI

Current MdePkg BaseLib has CalculateCrc32(). So, CRC32C and CRC16 can be added into BaseLib. If more modules need to consume Ucs2 <-> Utf8 conversion library, BaseUcs2Utf8Lib is generic enough to be

EXT4 (fourth extended filesystem) is a filesystem developed for Linux that has been in wide use (desktops, servers, smartphones) since 2008. The Ext4Pkg implements the Simple File System Protocol for

There is no other comment for this proposal. I will send it to edk2 devel mail list to collect the feedback. Thanks Liming

Thanks much everyone who attended 2 sessions of TDVF design review meeting and lots of valuable comments and feedbacks received. These 2 meetings were recorded and now uploaded to below link: Session

Thank you. A shorter SFF should not be a problem, as we use it anyway only for merging previously reviewed feature patch sets. I hope other community members are OK with this as

Laszlo: OK. I give the new proposed date for the release planning. SFF will be shorten to 5 days. HFF will be extended to 14 days. Date (00:00:00 UTC-8) Description 2021-05-28 Beginning of

I haven't even been aware of the "planning freeze". I think we can remove it. Regarding the HFF, I'd really suggest / request 14 calendar days. Thanks Laszlo

Laszlo: I understand this release requirement. Now, we have Feature Planning Freeze (1WW), Soft Feature Freeze (1WW) and Hard Feature Freeze (5 days). I would propose to remove Feature Planning

Sure. TDVF Design Review v0.95 is uploaded to https://bugzilla.tianocore.org/show_bug.cgi?id=3429 > Thanks Min

The mailing list still won't give me that file, can you update it in the bugzilla: https://bugzilla.tianocore.org/show_bug.cgi?id=3429 As well, please? Thanks, James

Thanks much for the comments and we don't want to make OvmfPkgX64.dsc over-complicated either. We have updated the design slides to V0.95 and Slides 6-15 are discussing the Config-A and Config-B.