Re: [RFC PATCH 0/4] KVM: x86/tdx: Have TDX handle VMXON during bringup

[<dan.j.williams@intel.com>]

dan.j.williams@ wrote:
[..]
> > > Sounds good and I read this as "hey, this is the form I would like to
> > > see, when someone else cleans this up and sends it back to me as a
> > > non-RFC".
> > 
> > Actually, I think I can take it forward.  Knock wood, but I don't think there's
> > all that much left to be done.  Heck, even writing the code for the initial RFC
> > was a pretty short adventure once I had my head wrapped around the concept.
> 
> Ack.

FYI, this series is now included in tsm.git#staging [1]. Chao had one
fixup to it [2].

Recall that tsm.git#staging is where all of us working on PCI Device
Security (TDX, SEV, and CCA) can start tripping over each others
implementations [3] in a unified tree. 

The initial core work in that tree is a v6.19 candidate as long as at
least one arch implementation is also ready. SEV looks nearly ready [4].
CCA will sit out as it is going through a specification update. TDX is
ready save for this vmxon dependency.

I recall being concerned about the new TDX always-on stance, but I now
think it is ok. Just puts more pressure on the dynamic-PAMT work to
land. In the meantime, disabling TDX in the BIOS is a stopgap for those
that can not tolerate the static-PAMT overhead.

[1]: https://git.kernel.org/pub/scm/linux/kernel/git/devsec/tsm.git/log/?h=staging
[2]: https://git.kernel.org/pub/scm/linux/kernel/git/devsec/tsm.git/commit/?id=406cd719d2a2
[3]: https://git.kernel.org/pub/scm/linux/kernel/git/devsec/tsm.git/commit/?id=e3d238ddeec0
[4]: http://lore.kernel.org/20251111063819.4098701-1-aik@amd.com