mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>
To: "Annapurve, Vishal" <vannapurve@google.com>,
	"seanjc@google.com" <seanjc@google.com>
Cc: "liam.merwick@oracle.com" <liam.merwick@oracle.com>,
	"Kohler, Jon" <jon@nutanix.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"thomas.lendacky@amd.com" <thomas.lendacky@amd.com>,
	"Zhao, Yan Y" <yan.y.zhao@intel.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"pbonzini@redhat.com" <pbonzini@redhat.com>,
	"Amit.Shah@amd.com" <Amit.Shah@amd.com>,
	"michael.roth@amd.com" <michael.roth@amd.com>
Subject: Re: [ANNOUNCE] PUCK Agenda - 2025.06.18 - Any topics?
Date: Fri, 20 Jun 2025 23:51:45 +0000	[thread overview]
Message-ID: <b9722d7f691f3aa32c4c725139a99ad49902aacb.camel@intel.com> (raw)
In-Reply-To: <20250617210100.514888-1-seanjc@google.com>

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

      reply	other threads:[~2025-06-20 23:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-17 21:01 Sean Christopherson
2025-06-20 23:51 ` Edgecombe, Rick P [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b9722d7f691f3aa32c4c725139a99ad49902aacb.camel@intel.com \
    --to=rick.p.edgecombe@intel.com \
    --cc=Amit.Shah@amd.com \
    --cc=jon@nutanix.com \
    --cc=kvm@vger.kernel.org \
    --cc=liam.merwick@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael.roth@amd.com \
    --cc=pbonzini@redhat.com \
    --cc=seanjc@google.com \
    --cc=thomas.lendacky@amd.com \
    --cc=vannapurve@google.com \
    --cc=yan.y.zhao@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®