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 3/5] migrate: Move repair_sock_init() to vu_init()
Date: Thu, 30 Jan 2025 19:33:28 +1100 [thread overview]
Message-ID: <20250130083330.917030-4-david@gibson.dropbear.id.au> (raw)
In-Reply-To: <20250130083330.917030-1-david@gibson.dropbear.id.au>
Currently we call repair_sock_init() immediately before
tap_sock_unix_init(). However, this means it will be skipped if the
vhost-user control fd is passed with --fd instead of being created at a
specific path. We still need the repair socket in that case.
Move it, instead, to vu_init(), which has the added advantage of moving
all migration related one-time init to the same place.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
---
tap.c | 3 ---
vhost_user.c | 3 +++
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/tap.c b/tap.c
index 3659aabd..d1a9f522 100644
--- a/tap.c
+++ b/tap.c
@@ -56,7 +56,6 @@
#include "netlink.h"
#include "pasta.h"
#include "packet.h"
-#include "repair.h"
#include "tap.h"
#include "log.h"
#include "vhost_user.h"
@@ -1362,8 +1361,6 @@ void tap_backend_init(struct ctx *c)
tap_sock_tun_init(c);
break;
case MODE_VU:
- repair_sock_init(c);
- /* fall through */
case MODE_PASST:
tap_sock_unix_init(c);
diff --git a/vhost_user.c b/vhost_user.c
index bbbf504f..5df29c47 100644
--- a/vhost_user.c
+++ b/vhost_user.c
@@ -44,6 +44,7 @@
#include "tap.h"
#include "vhost_user.h"
#include "pcap.h"
+#include "repair.h"
/* vhost-user version we are compatible with */
#define VHOST_USER_VERSION 1
@@ -1106,8 +1107,10 @@ void vu_init(struct ctx *c)
}
c->vdev->log_table = NULL;
c->vdev->log_call_fd = -1;
+
c->vdev->device_state_fd = -1;
c->vdev->device_state_result = -1;
+ repair_sock_init(c);
}
--
@@ -44,6 +44,7 @@
#include "tap.h"
#include "vhost_user.h"
#include "pcap.h"
+#include "repair.h"
/* vhost-user version we are compatible with */
#define VHOST_USER_VERSION 1
@@ -1106,8 +1107,10 @@ void vu_init(struct ctx *c)
}
c->vdev->log_table = NULL;
c->vdev->log_call_fd = -1;
+
c->vdev->device_state_fd = -1;
c->vdev->device_state_result = -1;
+ repair_sock_init(c);
}
--
2.48.1
next prev parent reply other threads:[~2025-01-30 8:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-30 8:33 [PATCH 0/5] RFC: Assorted migration improvements David Gibson
2025-01-30 8:33 ` [PATCH 1/5] migrate: Add passt-repair to .gitignore David Gibson
2025-01-30 8:33 ` [PATCH 2/5] migrate: vu_migrate_{source,target}() aren't actually vu speciic David Gibson
2025-01-30 8:33 ` David Gibson [this message]
2025-01-30 8:33 ` [PATCH 4/5] migrate: Make more handling common rather than vhost-user specific David Gibson
2025-01-30 8:33 ` [PATCH 5/5] migrate: Don't handle the migration channel through epoll David Gibson
2025-01-31 5:37 ` Stefano Brivio
2025-01-30 8:46 ` [PATCH 0/5] RFC: Assorted migration improvements Stefano Brivio
2025-01-30 8:55 ` David Gibson
2025-01-31 5:46 ` 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=20250130083330.917030-4-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).