On 3/25/2023 4:43 PM, Zhi Wang wrote:
On Sun, 12 Mar 2023 10:55:40 -0700 isaku.yamahata@xxxxxxxxx wrote: Does this have to be a new generic ioctl with a dedicated new x86_ops? SNP does not use it at all and all the system-scoped ioctl of SNP going through the CCP driver. So getting system-scope information of TDX/SNP will end up differently. Any thought, Sean? Moving getting SNP system-wide information to KVM dev ioctl seems not ideal and TDX does not have a dedicated driver like CCP. Maybe make this ioctl TDX-specific? KVM_TDX_DEV_OP?
What's the real different of it? For me, it's just renaming KVM_MEMORY_ENCRYPT_OP to KVM_TDX_DEV_OP and maybe add some error message if the IOCTL is issued for AMD plaform.
