Hi y'all, I'm just getting up to speed with the standards process now that we've determined the only way to get lazy accept support for SEV-SNP without extra information about what's being booted is to add a GetMemoryMapEx that takes a "supported features" argument.
I saw the final draft was sent to forum members not too long ago, and if we miss 2.10 on this, then AMD SEV-SNP boot times will be several seconds slower on VMs with large memory footprints. I have a pretty trivial change that builds on top of changes Jiewen Yao and Jiaqi Gao have proposed for TDX, but since those aren't yet merged, I'm not entirely sure what the right "code first" process is to make this proposal. I have the relevant commits cherry picked into a fork plus two from Google that add this new boot service. It'd be great for a guest OS to be able to opt into unaccepted memory support given a UEFI v2.10 version in the EFI system table. https://github.com/deeglaze/edk2/tree/getmemorymapex Relevant thread from qemu: https://www.mail-archive.com/qemu-devel@nongnu.org/msg894170.html Thanks y'all -- -Dionna Glaze, PhD (she/her) -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#91294): https://edk2.groups.io/g/devel/message/91294 Mute This Topic: https://groups.io/mt/92347337/21656 Group Owner: devel+ow...@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
