[ANNOUNCE] PUCK Agenda - 2025.06.18 - Any topics?

[ANNOUNCE] PUCK Agenda - 2025.06.18 - Any topics?

[Sean Christopherson]

I won't be able to make PUCK tomorrow, but that doesn't mean y'all can't meet
without me.  I _think_ if someone hits "Record", it will show up in my Google
Drive (because I'm the meeting owner), and then I can get it uploaded to the
shared drive.  So, someone just needs to take charge tomorrow :-)

Alternatively, if no one has anything to discuss, we can just cancel outright.
But IIRC, Paolo is out the next two weeks, so this may be your last chance to
pester him for a while.

Sorry for the late notice, this week has been a bit hectic.

Re: [ANNOUNCE] PUCK Agenda - 2025.06.18 - Any topics?

[Edgecombe, Rick P]

There are an increasing number of TDX intersecting patchsets flying around or
being alluded to. I was thinking it could help to have a discussion on how they
are all going to come together.
 - What parts do we want to do iteratively vs co-designed?
 - How to avoid duplicate work like debugging bugs in dependencies that are
already fixed in private?
 - What order to do them upstream?
 - How to evaluate/test Linux guests for features that don't have qemu support?
 - Others?

Of course some of these series' are not TDX specific. But in the TDX neck of the
woods, there seems to be a bit of a gap in common understanding.

Is a TDX focused discussion useful? Could we do it as a PUCK call agenda item?

Thanks,

Rick