From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: passt-dev@passt.top
Subject: Re: [PATCH v13 1/6] migrate: Skeleton of live migration logic
Date: Mon, 10 Feb 2025 13:26:02 +1100 [thread overview]
Message-ID: <Z6ljuiNWs87J-_Un@zatzit> (raw)
In-Reply-To: <20250209222005.1640077-2-sbrivio@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1949 bytes --]
On Sun, Feb 09, 2025 at 11:20:00PM +0100, Stefano Brivio wrote:
> Introduce facilities for guest migration on top of vhost-user
> infrastructure. Add migration facilities based on top of the current
> vhost-user infrastructure, moving vu_migrate() and related functions
> to migrate.c.
>
> Versioned migration stages define function pointers to be called on
> source or target, or data sections that need to be transferred.
>
> The migration header consists of a magic number, a version number for the
> encoding, and a "compat_version" which represents the oldest version which
> is compatible with the current one. We don't use it yet, but that allows
> for the future possibility of backwards compatible protocol extensions.
>
> Co-authored-by: David Gibson <david@gibson.dropbear.id.au>
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
> Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
with the exception of one nit, which I hope to send a fixup patch for today:
[snip]
> +/**
> + * struct migrate_stage - Callbacks and parameters for one stage of migration
> + * @name: Stage name (for debugging)
> + * @source: Callback to implement this stage on the source
> + * @target: Callback to implement this stage on the target
> + * @iov: Optional data section to transfer
> + */
> +struct migrate_stage {
> + const char *name;
> + int (*source)(struct ctx *c, const struct migrate_stage *stage, int fd);
> + int (*target)(struct ctx *c, const struct migrate_stage *stage, int fd);
> +
> + /* Add here separate rollback callbacks if needed */
> +
> + struct iovec iov;
We're no longer using this @iov field, and it can be removed.
--
David Gibson (he or they) | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you, not the other way
| around.
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-02-10 2:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-09 22:19 [PATCH v13 0/6] State migration, kind of draft again Stefano Brivio
2025-02-09 22:20 ` [PATCH v13 1/6] migrate: Skeleton of live migration logic Stefano Brivio
2025-02-10 2:26 ` David Gibson [this message]
2025-02-09 22:20 ` [PATCH v13 2/6] migrate: Migrate guest observed addresses Stefano Brivio
2025-02-09 22:20 ` [PATCH v13 3/6] Add interfaces and configuration bits for passt-repair Stefano Brivio
2025-02-10 2:59 ` David Gibson
2025-02-10 15:54 ` Stefano Brivio
2025-02-09 22:20 ` [PATCH v13 4/6] vhost_user: Make source quit after reporting migration state Stefano Brivio
2025-02-10 3:43 ` David Gibson
2025-02-09 22:20 ` [PATCH v13 5/6] migrate: Migrate TCP flows Stefano Brivio
2025-02-10 6:05 ` David Gibson
2025-02-10 9:51 ` Stefano Brivio
2025-02-10 15:54 ` Stefano Brivio
2025-02-09 22:20 ` [PATCH v13 6/6] test: Add migration tests Stefano Brivio
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=Z6ljuiNWs87J-_Un@zatzit \
--to=david@gibson.dropbear.id.au \
--cc=passt-dev@passt.top \
--cc=sbrivio@redhat.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.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for IMAP folder(s).