From: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>
To: "thomas.lendacky@amd.com" <thomas.lendacky@amd.com>,
"pankaj.gupta@amd.com" <pankaj.gupta@amd.com>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"seanjc@google.com" <seanjc@google.com>
Cc: "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: PUCK coco migration topic
Date: Tue, 11 Aug 2026 17:32:48 +0000 [thread overview]
Message-ID: <78aa2a375ce92ac37f084dc44ff8ee126b7ffd22.camel@intel.com> (raw)
Can we steal 15-20 minutes at PUCK tomorrow for a little sync on TDX migration?
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.
Rick
next reply other threads:[~2026-08-11 17:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 17:32 Edgecombe, Rick P [this message]
2026-08-11 22:12 ` PUCK coco migration topic Sean Christopherson
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=78aa2a375ce92ac37f084dc44ff8ee126b7ffd22.camel@intel.com \
--to=rick.p.edgecombe@intel.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=seanjc@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.