From: Sean Christopherson <seanjc@google.com>
To: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>
Cc: "thomas.lendacky@amd.com" <thomas.lendacky@amd.com>,
"pankaj.gupta@amd.com" <pankaj.gupta@amd.com>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"Maloor, Kishen" <kishen.maloor@intel.com>,
"Bityutskiy, Artem" <artem.bityutskiy@intel.com>,
"Lindgren, Tony" <tony.lindgren@intel.com>
Subject: Re: PUCK coco migration topic
Date: Tue, 11 Aug 2026 22:12:06 +0000 [thread overview]
Message-ID: <anueNuwFl_dNRKBo@google.com> (raw)
In-Reply-To: <78aa2a375ce92ac37f084dc44ff8ee126b7ffd22.camel@intel.com>
On Tue, Aug 11, 2026, Edgecombe, Rick P wrote:
> Can we steal 15-20 minutes at PUCK tomorrow for a little sync on TDX migration?
Yep, as usual, there's nothing on the agenda.
> We want to share a high level of what we are working on for the sake of less
> surprise later, and also to sync with the SNP work.
Don't worry, nothing will make me have a more negative view of live migrating
CoCo VMs than I already have ;-)
prev parent reply other threads:[~2026-08-11 22:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 17:32 PUCK coco migration topic Edgecombe, Rick P
2026-08-11 22:12 ` Sean Christopherson [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=anueNuwFl_dNRKBo@google.com \
--to=seanjc@google.com \
--cc=artem.bityutskiy@intel.com \
--cc=kishen.maloor@intel.com \
--cc=kvm@vger.kernel.org \
--cc=pankaj.gupta@amd.com \
--cc=pbonzini@redhat.com \
--cc=rick.p.edgecombe@intel.com \
--cc=thomas.lendacky@amd.com \
--cc=tony.lindgren@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