From: David Gibson <david@gibson.dropbear.id.au>
To: passt-dev@passt.top, Stefano Brivio <sbrivio@redhat.com>
Cc: David Gibson <david@gibson.dropbear.id.au>
Subject: [PATCH v14 02/14] fixup: Remove unused iov field in struct migrate_stage
Date: Mon, 10 Feb 2025 20:17:53 +1100 [thread overview]
Message-ID: <20250210091805.2261228-3-david@gibson.dropbear.id.au> (raw)
In-Reply-To: <20250210091805.2261228-1-david@gibson.dropbear.id.au>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
---
migrate.h | 3 ---
1 file changed, 3 deletions(-)
diff --git a/migrate.h b/migrate.h
index d2997795..2c51cd97 100644
--- a/migrate.h
+++ b/migrate.h
@@ -24,7 +24,6 @@ struct migrate_header {
* @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;
@@ -32,8 +31,6 @@ struct migrate_stage {
int (*target)(struct ctx *c, const struct migrate_stage *stage, int fd);
/* Add here separate rollback callbacks if needed */
-
- struct iovec iov;
};
/**
--
@@ -24,7 +24,6 @@ struct migrate_header {
* @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;
@@ -32,8 +31,6 @@ struct migrate_stage {
int (*target)(struct ctx *c, const struct migrate_stage *stage, int fd);
/* Add here separate rollback callbacks if needed */
-
- struct iovec iov;
};
/**
--
2.48.1
next prev parent reply other threads:[~2025-02-10 9:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 9:17 [PATCH v14 00/14] State migration David Gibson
2025-02-10 9:17 ` [PATCH v14 01/14] migrate: Skeleton of live migration logic David Gibson
2025-02-10 9:17 ` David Gibson [this message]
2025-02-10 9:17 ` [PATCH v14 03/14] migrate: Migrate guest observed addresses David Gibson
2025-02-10 9:17 ` [PATCH v14 04/14] Add interfaces and configuration bits for passt-repair David Gibson
2025-02-10 9:17 ` [PATCH v14 05/14] fixup: Reorder conf options David Gibson
2025-02-10 9:17 ` [PATCH v14 06/14] fixup: Correctly type repair_cmd global David Gibson
2025-02-10 9:17 ` [PATCH v14 07/14] fixup: Sanity check passt-repair reply message David Gibson
2025-02-10 9:17 ` [PATCH v14 08/14] fixup: Don't close repair socket after first migration attempt David Gibson
2025-02-10 9:18 ` [PATCH v14 09/14] vhost_user: Make source quit after reporting migration state David Gibson
2025-02-10 9:18 ` [PATCH v14 10/14] fixup: Adjust conditions under which we quite after completing migration David Gibson
2025-02-10 9:18 ` [PATCH v14 11/14] migrate: Migrate TCP flows David Gibson
2025-02-10 9:18 ` [PATCH v14 12/14] fixup: Check for errors on repair mode rollback David Gibson
2025-02-10 9:18 ` [PATCH v14 13/14] test: Add migration tests David Gibson
2025-02-10 9:18 ` [PATCH v14 14/14] WIP: migrate, tcp: Shrink windows before migration David Gibson
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=20250210091805.2261228-3-david@gibson.dropbear.id.au \
--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).