Hi Dave, On 11/11/22 10:35 AM, Dave Hansen wrote: > This is *NOT* "a wrapper to get TDREPORT from the TDX Module", this is > at best "a wrapper to get TDREPORT sub type 0 from the TDX Module". In both the commit log and the comments, I can highlight the "subtype 0" information. Will that work for you, or do you prefer that this wrapper take the "subtype" option as argument and we pass 0 for the subtype value from the TDX guest driver? > > It also occurs to me that "sub type 0" could use an actual name. Could > we give it one, please? Although the subtype option is mentioned in the TDX Module spec, it is not currently used (it expects this value to be zero), and the spec also does not explain why this option is required. According to TDX architects, this option was primarily added to handle any future requirements that may arise that require additional information to be added to the TDREPORT. However, they do not currently have any valid use cases for it. So the current version can only be described as "Type-0." Once a new use case for Subtype 1 is defined, we may be able to come up with a suitable name. Are you okay with calling it "Type-0" for the time being? -- Sathyanarayanan Kuppuswamy Linux Kernel Developer
