From: Sean Christopherson <seanjc@google.com>
To: Sean Christopherson <seanjc@google.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Rick P Edgecombe <rick.p.edgecombe@intel.com>,
Isaku Yamahata <isaku.yamahata@intel.com>,
Wei W Wang <wei.w.wang@intel.com>,
David Skidmore <davidskidmore@google.com>,
Steve Rutherford <srutherford@google.com>,
Pankaj Gupta <pankaj.gupta@amd.com>
Subject: [ANNOUNCE] PUCK Agenda - 2024.04.03 - TDX upstreaming strategy
Date: Tue, 2 Apr 2024 17:25:54 -0700 [thread overview]
Message-ID: <20240403002554.418953-1-seanjc@google.com> (raw)
The primary topic for tomorrow is how to get the beast that is TDX across the
merge finish line.
If time permits, and no one has other topics, live migration support for TDX
and SNP might also be discussed, but I don't expect that to be much more than a
high-level overview-ish discussion at this point. In other words, I honestly
wouldn't join *just* for the (potential) live migration discussion.
Future Schedule:
April 10th - Available
April 17th - Available
April 24th - Available
reply other threads:[~2024-04-03 0:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240403002554.418953-1-seanjc@google.com \
--to=seanjc@google.com \
--cc=davidskidmore@google.com \
--cc=isaku.yamahata@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pankaj.gupta@amd.com \
--cc=rick.p.edgecombe@intel.com \
--cc=srutherford@google.com \
--cc=wei.w.wang@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®