Re: [PATCH v5 06/12] x86/tdx: Get TD execution environment information via TDINFO

[Kuppuswamy, Sathyanarayanan]

On 8/20/21 11:58 AM, Andi Kleen wrote:
> Without working TDCALLs the error message won't appear anywhere. The only practical way to debug 
> such a problem is a kernel debugger.
>
> Also printing an error message might end up recursing because the console write would trigger TDCALL 
> again, or eventually stop because the console lock is already taken. In any case it won't work.

Yes, good point. In this case, adding debug print will not work. But I
can add more comments to the code.

--
Sathyanarayanan Kuppuswamy
Linux Kernel Developer