From: "Serge E. Hallyn" <serge@hallyn.com>
To: Artem Bityutskiy <dedekind1@gmail.com>
Cc: "Serge Hallyn (AMD)" <sergeh@kernel.org>,
"Peter Xu" <peterx@redhat.com>,
"Tony Lindgren" <tony.lindgren@linux.intel.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Sean Christopherson" <seanjc@google.com>,
"Fabiano Rosas" <farosas@suse.de>,
"Jon Grimm" <Jon.Grimm@amd.com>,
"Pankaj Gupta" <pankaj.gupta@amd.com>,
"Tom Lendacky" <thomas.lendacky@amd.com>,
"Marc Zyngier" <maz@kernel.org>,
"Oliver Upton" <oliver.upton@linux.dev>,
"Steven Price" <steven.price@arm.com>,
"Anup Patel" <anup@brainfault.org>,
"Samuel Ortiz" <sameo@rivosinc.com>,
"Jakub Růžička" <jakub.ruzicka@matfyz.cz>,
"Jörg Rödel" <joro@8bytes.org>,
"Vishal Annapurve" <vannapurve@google.com>,
"Elena Reshetova" <elena.reshetova@intel.com>,
"Kai Huang" <kai.huang@intel.com>,
"Kishen Maloor" <kishen.maloor@intel.com>,
"Mika Westerberg" <mika.westerberg@linux.intel.com>,
"Peter Fang" <peter.fang@intel.com>,
"Rick Edgecombe" <rick.p.edgecombe@intel.com>,
"Xiaoyao Li" <xiaoyao.li@intel.com>,
"Xu Yilun" <yilun.xu@linux.intel.com>,
kvm@vger.kernel.org, David.Kaplan@amd.com,
Mathias.Brossard@arm.com
Subject: Re: TDX migration model
Date: Thu, 5 Nov 2026 10:42:24 -0600 [thread overview]
Message-ID: <auyx8C67zCnbPpuL@hallyn.com> (raw)
In-Reply-To: <85f899cd277b2188cd4b33f8f21b206fa2ff6f6f.camel@gmail.com>
On Thu, Nov 05, 2026 at 05:59:01PM +0200, Artem Bityutskiy wrote:
> [I dropped a bunch of people from CC, sorry about that, just restored the CC
> list]
>
> On Thu, 2026-11-05 at 08:58 -0600, Serge Hallyn (AMD) wrote:
> > On Wed, Nov 04, 2026 at 03:51:45PM +0200, Artem Bityutskiy wrote:
> > > Hi Peter, community,
> > >
> > > Here is the TDX migration model doc that I mentioned in the CoCo migration
> > > uAPI thread:
> > >
> > > https://github.com/dedekind/dedekind-share/blob/master/2026/tdx-live-migration.md
> > >
> > > The doc focuses on TDX only. It does not cover CoCo in general or
> > > Linux/KVM.
> > >
> > > The goal is to lay out what the TDX module offers in terms of ABI and
> > > migration flow today. Hopefully it is easier to read than the TDX specs,
> > > which are much more detailed. Feedback is very welcome.
> > >
> > > The uAPIs that we suggested were modeled around this flow and ABI. But
> > > we kept general CoCo VMs in mind as much as we could.
> > >
> > > The TDX live migration PoC implementation that we mentioned earlier follows
> > > the flows and uses the ABIs described in the doc.
> > >
> > > Thanks!
> > >
> > > P.S. From the ARM talk and hallway conversations at Plumbers, I understood
> > > that the ARM live migration flow is very similar to TDX. For SNP guests, we
> > > have not heard enough yet.
> > >
> > > Thanks,
> > > Artem.
> >
> > Thanks, Artem!
> >
> > So, looking at the section '### How the Setup Session Works', is it safe
> > to assume that you are using the qemu migration fd for the message
> > transfers? So basically qemu loops over KVM_MIGRATE_SETUP calls, which
> > is directed to platform-specific handlers, which in the tdx case calls
> > TDH.MIG.SETUP, and this loop continues until TDX_SUCCESS? If so, great,
> > that mirrors pretty exactly what we were looking at for SNP.
>
> Hi,
>
> Yes, that's the flow. I’m not sure about the migration fd part, I believe we
> pass the setup session data via ioctl buffers. I am sure Kishen will can
> clarify.
If you mean pass via ioctl buffers from tdx->kvm-> back to qemu, which passes
it over the migration fd to the other side, then that's what I expected.
Othewise I'll be interested to the details :)
thanks,
-serge
next prev parent reply other threads:[~2026-11-05 16:42 UTC|newest]
Thread overview: 100+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 7:13 [RFC PATCH v2 0/4] Add KVM API for confidential guest live migration Tony Lindgren
2026-08-31 7:13 ` [RFC PATCH v2 1/4] Documentation: KVM: Add live migration API for confidential guests Tony Lindgren
2026-08-31 7:20 ` sashiko-bot
2026-09-18 11:35 ` Peter Xu
2026-09-21 4:20 ` Tony Lindgren
2026-09-24 1:50 ` Wei Wang
2026-09-24 4:51 ` Tony Lindgren
2026-11-10 12:42 ` Artem Bityutskiy
2026-08-31 7:13 ` [RFC PATCH v2 2/4] KVM: x86: Add optional KVM_CAP_LIVE_MIGRATION and KVM_MIGRATE_CMD Tony Lindgren
2026-08-31 7:23 ` sashiko-bot
2026-09-01 6:03 ` Tony Lindgren
2026-09-07 11:53 ` Tony Lindgren
2026-09-07 13:15 ` Jörg Rödel
2026-09-07 13:32 ` Artem Bityutskiy
2026-09-08 4:15 ` Tony Lindgren
2026-09-08 4:43 ` Tony Lindgren
2026-09-09 0:22 ` Kishen Maloor
2026-09-09 6:57 ` Tony Lindgren
2026-09-10 1:11 ` Kishen Maloor
2026-09-10 6:33 ` Tony Lindgren
2026-09-11 1:40 ` Kishen Maloor
2026-09-11 4:23 ` Tony Lindgren
2026-09-15 0:14 ` Kishen Maloor
2026-09-15 4:44 ` Tony Lindgren
2026-09-15 15:53 ` Kishen Maloor
2026-09-16 5:09 ` Tony Lindgren
2026-09-17 3:31 ` Kishen Maloor
2026-09-17 6:42 ` Tony Lindgren
2026-09-18 4:32 ` Kishen Maloor
2026-09-18 5:58 ` Tony Lindgren
2026-09-21 0:13 ` Kishen Maloor
2026-09-21 6:52 ` Tony Lindgren
2026-09-21 9:24 ` Tony Lindgren
2026-09-21 10:58 ` Tony Lindgren
2026-09-22 3:57 ` Kishen Maloor
2026-09-22 5:25 ` Tony Lindgren
2026-09-23 0:38 ` Kishen Maloor
2026-09-23 6:04 ` Tony Lindgren
2026-09-24 5:53 ` Kishen Maloor
2026-09-24 6:59 ` Tony Lindgren
2026-09-18 4:33 ` Kishen Maloor
2026-09-21 5:58 ` Tony Lindgren
2026-09-21 6:56 ` Tony Lindgren
2026-09-22 3:56 ` Kishen Maloor
2026-09-22 6:27 ` Tony Lindgren
2026-09-23 0:37 ` Kishen Maloor
2026-09-23 6:50 ` Tony Lindgren
2026-09-24 5:34 ` Kishen Maloor
2026-09-24 7:15 ` Tony Lindgren
2026-10-08 9:22 ` Tony Lindgren
2026-10-16 4:00 ` Kishen Maloor
2026-08-31 7:13 ` [RFC PATCH v2 3/4] KVM: x86: Add optional KVM_EXPORT_MEMORY and KVM_IMPORT_MEMORY Tony Lindgren
2026-08-31 7:23 ` sashiko-bot
2026-09-01 6:10 ` Tony Lindgren
2026-08-31 7:13 ` [RFC PATCH v2 4/4] KVM: x86: Add optional KVM_EXPORT_VCPU and KVM_IMPORT_VCPU Tony Lindgren
2026-08-31 7:23 ` sashiko-bot
2026-09-01 6:12 ` Tony Lindgren
2026-09-04 18:24 ` [RFC PATCH v2 0/4] Add KVM API for confidential guest live migration Artem Bityutskiy
2026-09-17 21:27 ` Peter Xu
2026-09-18 12:46 ` Artem Bityutskiy
2026-09-18 15:53 ` Peter Xu
2026-09-22 8:09 ` Artem Bityutskiy
2026-09-22 9:42 ` Tony Lindgren
2026-09-22 11:54 ` Artem Bityutskiy
2026-09-23 4:20 ` Tony Lindgren
2026-09-22 21:18 ` Peter Xu
2026-09-23 12:05 ` Artem Bityutskiy
2026-09-24 21:19 ` Peter Xu
2026-09-28 14:15 ` Artem Bityutskiy
2026-09-29 21:05 ` Peter Xu
2026-10-02 19:57 ` Artem Bityutskiy
2026-10-07 20:00 ` Peter Xu
2026-09-23 15:28 ` Serge Hallyn (AMD)
2026-11-04 13:51 ` TDX migration model Artem Bityutskiy
2026-11-05 14:58 ` Serge Hallyn (AMD)
2026-11-05 15:59 ` Artem Bityutskiy
2026-11-05 16:42 ` Serge E. Hallyn [this message]
2026-11-06 2:00 ` Kishen Maloor
2026-11-09 7:45 ` Tony Lindgren
2026-11-09 22:15 ` Serge Hallyn (AMD)
2026-11-10 5:16 ` Tony Lindgren
2026-10-09 6:11 ` [RFC PATCH v2 0/4] Add KVM API for confidential guest live migration Tony Lindgren
2026-10-16 3:56 ` Kishen Maloor
2026-10-19 7:34 ` Tony Lindgren
2026-09-20 23:56 ` Kishen Maloor
2026-09-23 21:36 ` Peter Xu
2026-09-24 4:27 ` Kishen Maloor
2026-09-25 14:18 ` Peter Xu
2026-09-29 1:28 ` Kishen Maloor
2026-09-30 20:42 ` Peter Xu
2026-10-07 4:27 ` Kishen Maloor
2026-10-07 20:13 ` Peter Xu
2026-10-08 6:23 ` Tony Lindgren
2026-10-08 14:31 ` Peter Xu
2026-10-09 4:29 ` Tony Lindgren
2026-10-16 4:02 ` Kishen Maloor
2026-09-18 18:36 ` Ionut Mihalcea
2026-09-21 4:35 ` Tony Lindgren
2026-09-25 16:03 ` Serge Hallyn (AMD)
2026-09-28 3:24 ` Kishen Maloor
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=auyx8C67zCnbPpuL@hallyn.com \
--to=serge@hallyn.com \
--cc=David.Kaplan@amd.com \
--cc=Jon.Grimm@amd.com \
--cc=Mathias.Brossard@arm.com \
--cc=anup@brainfault.org \
--cc=dedekind1@gmail.com \
--cc=elena.reshetova@intel.com \
--cc=farosas@suse.de \
--cc=jakub.ruzicka@matfyz.cz \
--cc=joro@8bytes.org \
--cc=kai.huang@intel.com \
--cc=kishen.maloor@intel.com \
--cc=kvm@vger.kernel.org \
--cc=maz@kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=oliver.upton@linux.dev \
--cc=pankaj.gupta@amd.com \
--cc=pbonzini@redhat.com \
--cc=peter.fang@intel.com \
--cc=peterx@redhat.com \
--cc=rick.p.edgecombe@intel.com \
--cc=sameo@rivosinc.com \
--cc=seanjc@google.com \
--cc=sergeh@kernel.org \
--cc=steven.price@arm.com \
--cc=thomas.lendacky@amd.com \
--cc=tony.lindgren@linux.intel.com \
--cc=vannapurve@google.com \
--cc=xiaoyao.li@intel.com \
--cc=yilun.xu@linux.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.