Hi, On Mon, Aug 12, 2024 at 03:47:55PM -0700, Rick Edgecombe wrote: > The problem with this solution is that using, effectively > KVM_GET_SUPPORTED_CPUID internally, is not an effective way to filter the > CPUID bits. In practice, the spots where TDX support does the filtering > needed some adjustments. See the log of “Add CPUID bits missing from > KVM_GET_SUPPORTED_CPUID” for more information. We can generate a TDX suitable default CPUID configuration by adding KVM_GET_SUPPORTED_TDX_CPUID. This would handled similar to the existing KVM_GET_SUPPORTED_CPUID and KVM_GET_SUPPORTED_HV_CPUID. Or are there some reasons to avoid adding this? Regards, Tony