From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: passt-dev@passt.top
Subject: Re: [PATCH v13 4/6] vhost_user: Make source quit after reporting migration state
Date: Mon, 10 Feb 2025 14:43:35 +1100 [thread overview]
Message-ID: <Z6l150vn9XixCxL-@zatzit> (raw)
In-Reply-To: <20250209222005.1640077-5-sbrivio@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2112 bytes --]
On Sun, Feb 09, 2025 at 11:20:03PM +0100, Stefano Brivio wrote:
> This will close all the sockets we currently have open in repair mode,
> and completes our migration tasks as source. If the hypervisor wants
> to have us back at this point, somebody needs to restart us.
>
> Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
> ---
> vhost_user.c | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/vhost_user.c b/vhost_user.c
> index 256c8ab..9115fb5 100644
> --- a/vhost_user.c
> +++ b/vhost_user.c
> @@ -998,6 +998,9 @@ static bool vu_send_rarp_exec(struct vu_dev *vdev,
> return false;
> }
>
> +/* If set, quit when we get a VHOST_USER_CHECK_DEVICE_STATE, after replying */
> +static bool quit_on_device_state = false;
We don't actually need this global, because we have c->migrate_target.
> +
> /**
> * vu_set_device_state_fd_exec() - Set the device state migration channel
> * @vdev: vhost-user device
> @@ -1025,6 +1028,9 @@ static bool vu_set_device_state_fd_exec(struct vu_dev *vdev,
> migrate_request(vdev->context, msg->fds[0],
> direction == VHOST_USER_TRANSFER_STATE_DIRECTION_LOAD);
>
> + if (direction == VHOST_USER_TRANSFER_STATE_DIRECTION_SAVE)
> + quit_on_device_state = true;
> +
> /* We don't provide a new fd for the data transfer */
> vmsg_set_reply_u64(msg, VHOST_USER_VRING_NOFD_MASK);
>
> @@ -1203,4 +1209,10 @@ void vu_control_handler(struct vu_dev *vdev, int fd, uint32_t events)
>
> if (reply_requested)
> vu_send_reply(fd, &msg);
> +
> + if (quit_on_device_state &&
> + msg.hdr.request == VHOST_USER_CHECK_DEVICE_STATE) {
We probably also only want to quit when the migration is successful.
We can't determine that in all cases, but we can at least check
device_state_result. Patch coming.
> + info("Migration complete, exiting");
> + _exit(EXIT_SUCCESS);
> + }
> }
--
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 4:05 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
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 [this message]
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=Z6l150vn9XixCxL-@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).