From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: passt-dev@passt.top, Laurent Vivier <lvivier@redhat.com>
Subject: Re: [PATCH v5 6/6] Implement source and target sides of migration
Date: Wed, 5 Feb 2025 12:10:10 +1100 [thread overview]
Message-ID: <Z6K6cuOMdJibqWDO@zatzit> (raw)
In-Reply-To: <20250205003904.2797491-7-sbrivio@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1847 bytes --]
On Wed, Feb 05, 2025 at 01:39:04AM +0100, Stefano Brivio wrote:
> This implements flow preparation on the source, transfer of data with
> a format roughly inspired by struct tcp_tap_conn, and flow insertion
> on the target, with all the appropriate window options, window
> scaling, MSS, etc.
>
> The target side is rather convoluted because we first need to create
> sockets and switch them to repair mode, before we can apply options
> that are *not* stored in the flow table. However, we don't want to
> request repair mode for sockets one by one. So we need to do this in
> several steps.
>
> A hack in order to connect() on the "RARP" message should be easy to
> enable, I left a couple of comments in that sense.
>
> This is very much draft quality, but I tested the whole flow, and it
> works for me. Window parameters and MSS match, too.
>
> Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
[snip]
> diff --git a/isolation.c b/isolation.c
> index c944fb3..df58bb8 100644
> --- a/isolation.c
> +++ b/isolation.c
> @@ -377,7 +377,7 @@ void isolate_postfork(const struct ctx *c)
> {
> struct sock_fprog prog;
>
> - prctl(PR_SET_DUMPABLE, 0);
> +// prctl(PR_SET_DUMPABLE, 0);
Looks like a stray debugging change made it in here. Fwiw, I keep a
branch around with debugging hacks including exactly this. To make it
harder to accidentally leak debug hacks into "real" series, I usually
rebase between my debugging branch and main.
In this case it conflicted with the patch from my debugging branch, of
course, which is why I spotted it.
>
> switch (c->mode) {
> case MODE_PASST:
--
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 --]
prev parent reply other threads:[~2025-02-05 1:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-05 0:38 [PATCH v5 0/6] Draft, incomplete series introducing state migration Stefano Brivio
2025-02-05 0:38 ` [PATCH v5 1/6] Introduce facilities for guest migration on top of vhost-user infrastructure Stefano Brivio
2025-02-05 1:44 ` David Gibson
2025-02-05 0:39 ` [PATCH v5 2/6] migrate: Make more handling common rather than vhost-user specific Stefano Brivio
2025-02-05 0:39 ` [PATCH v5 3/6] migrate: Don't handle the migration channel through epoll Stefano Brivio
2025-02-05 0:39 ` [PATCH v5 4/6] Add interfaces and configuration bits for passt-repair Stefano Brivio
2025-02-05 0:39 ` [PATCH v5 5/6] vhost_user: Make source quit after reporting migration state Stefano Brivio
2025-02-05 2:09 ` David Gibson
2025-02-05 5:47 ` Stefano Brivio
2025-02-05 8:58 ` Hanna Czenczek
2025-02-05 10:19 ` Stefano Brivio
2025-02-05 11:39 ` David Gibson
2025-02-05 0:39 ` [PATCH v5 6/6] Implement source and target sides of migration Stefano Brivio
2025-02-05 1:10 ` David Gibson [this message]
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=Z6K6cuOMdJibqWDO@zatzit \
--to=david@gibson.dropbear.id.au \
--cc=lvivier@redhat.com \
--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).