* Andi KMaybe. There might well be differences in the contents as you say. So far SVKL doesn't really exist yet, initially there will be the initrd based agents. The agents definitely will need to know about TDX.
Is there any way we could merge these two so that the TDX/SVKL would
look similar to SEV/ES to userspace? If we needed some initrd glue here
for luks it would be great if we could have one piece of glue.
[I'm not sure if the numbering/naming of the secrets, and their format
are defined in the same way]
Do you think the ioctl is preferable to read+ftruncate/unlink ?
And if it was an ioctl, again could we get some standardisation here -
i.e.
maybe a /dev/confguest with a CONF_COMP_GET_KEY etc ?