Re: [RFC PATCH 06/15] virt: tdx-guest: Support TDI bind and unbind operations

[Edgecombe, Rick P]

On Tue, 2026-11-03 at 08:49 +0000, Duan, Zhenzhong wrote:
> 
> > -----Original Message-----
> > From: Edgecombe, Rick P <rick.p.edgecombe@xxxxxxxxx>
> > On Thu, 2026-10-29 at 03:26 +0000, Duan, Zhenzhong wrote:
> > > I want to discuss this further.
> > > 
> > > If the TSM driver successfully locks a device but later fails to unlock
> > it,
> > 
> > Can you explain some concrete scenarios where this would happen? We can
> > think
> > about whether it is required for an initial minimal set that does something
> > useful.
> 
> I can think of some rare cases: the TDCM hypercall may return an error(e.g., a messing VMM or TDI device firmware),
> 

I'm not clear whose fault this is.

>  or TDCM hypercall polling timeout(e.g., heavy load in host).

Heavy load in the host leads to broken flag being set? This is pretty similar to
the issues around the BUSY errors. You really need to think through how this is
all going to work.