Hi, > Well that's a good question. If we expect the same target (CloudHv) to > support both TDX and non-TDX, that means the generated TDVF will be a > PVH ELF binary, which will require some special handling from Cloud > Hypervisor. > Having two separate targets would simplify things a lot. What's the > plan for QEMU? Will the same OVMF target cover both use cases?
Yes, there will be a single binary supporting both tdx and non-tdx, some configs add sev to the mix. Doing the same for cloudhv shouldn't be much of a problem I think. In tdx mode the firmware uses the tdhob for memory detection, in non-tdx mode qemu fw_cfg is used instead. The cloudhv build could switch between tdhob and pvhinfo in a simliar way. take care, Gerd -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#86902): https://edk2.groups.io/g/devel/message/86902 Mute This Topic: https://groups.io/mt/89319389/21656 Group Owner: devel+ow...@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
