Re: [RFC PATCH 06/15] x86/virt/tdx: Initialize Quoting extension during bringup

[Edgecombe, Rick P]

On Sun, 2026-06-14 at 00:50 -0700, Peter Fang wrote:
> > Is this micro-optimization worth it? What are the classes of quote-init
> > failures vs just make the policy be anything in the module must init.
> 
> Since there is a fallback option to do the Quoting in userspace, I think
> it is probably not worth shooting down TDX entirely over quote-init
> failures.
> 
> The quote-init failures can come from:
> 
>   1. Quoting init SEAMCALL failures, which look pretty opaque to the
>      kernel and there's not much it can do about it.
>   2. Quoting buffer allocation failures, which *are* understood by the
>      kernel, and it could maybe try something else. Right now, we just
>      treat it the same as 1.
> 
> This is helpful because I think the question of "what if the Quoting
> extension fails" has come up enough times that it warrants some
> explanation in the patch log. Thanks.

I thought we were going to do:
- If quoting is not supported, don't try to init quoting, and don't fail init
over it.
- If quoting is supported, but fails to init. Just fail TDX initialization for
simplicity.

This is what we are doing for the other features.