From: Andrey Drobyshev <andrey.drobyshev@virtuozzo.com>
To: qemu-devel@nongnu.org
Cc: mst@redhat.com, sgarzare@redhat.com, farosas@suse.de,
peterx@redhat.com, dongli.zhang@oracle.com, bchaney@akamai.com,
mark.kanda@oracle.com, den@openvz.org,
mail@maciej.szmigiero.name
Subject: Re: [PATCH v3 0/7] migration/cpr: support vhost-vsock devices
Date: Tue, 18 Aug 2026 14:02:10 +0300 [thread overview]
Message-ID: <dadd79c2-89c7-405a-b2c9-7973c3fe62d1@virtuozzo.com> (raw)
In-Reply-To: <f335aadd-1157-4a57-bd8c-18bd6b76582c@virtuozzo.com>
On 8/11/26 5:12 PM, Andrey Drobyshev wrote:
> On 6/30/26 9:35 PM, Maciej S. Szmigiero wrote:
>> On 26.06.2026 18:46, Andrey Drobyshev wrote:
>>> v2 -> v3:
>>>
>>> Re-design device ownership hand-off (suggested by Dongli). Do not rely
>>> on SETUP migration notifiers, as this approach forces us to reorder
>>> generic migration code (see v2 discussion). Instead:
>>>
>>> * .pre_save() releases ownership on the source (RESET_OWNER) once VM
>>> is stopped;
>>> * .realize() is adjusted to defer device ownership acquisition for an
>>> incoming CPR;
>>> * .post_load() actually claims the device (VHOST_SET_OWNER);
>>> * FAILED migration event callback re-aquires the ownership on the
>>> source after re_save released it.
>>>
>>> v2: https://lore.kernel.org/qemu-devel/57c9c9b3-d758-489b-95b8-d16c258b9b0c@virtuozzo.com
>>>
>>> Andrey Drobyshev (7):
>>> vhost: add vhost_reset_owner op
>>> vhost-vsock: don't reset connections during CPR
>>> vhost-vsock: fix FD leak in realize()
>>> vhost-vsock: preserve vhost FD during CPR
>>> vhost: factor out vhost_dev_init_backend()
>>> vhost: add vhost_dev_set_owner() / vhost_dev_reset_owner() helpers
>>> vhost-vsock: hand off device ownership across CPR
>>>
>> These patches look okay CPR-wise, so:
>> Acked-by: Maciej S. Szmigiero <maciej.szmigiero@oracle.com> # for CPR
>>
>> But the vsock parts still need review by their maintainers/reviewers.
>>
>> Thanks,
>> Maciej
>>
>
> FYI the kernel counterpart series adding VHOST_RESET_OWNER ioctl to
> vsock ended up in Michael's vhost tree ([1], commits
> 6236e765f16d^..c7bfb8815d83).
>
> Therefore - friendly ping for this series.
>
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git
>
> Andrey
Another friendly ping
next prev parent reply other threads:[~2026-08-18 11:08 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-26 16:46 [PATCH v3 0/7] migration/cpr: support vhost-vsock devices Andrey Drobyshev
2026-06-26 16:46 ` [PATCH v3 1/7] vhost: add vhost_reset_owner op Andrey Drobyshev
2026-06-26 16:46 ` [PATCH v3 2/7] vhost-vsock: don't reset connections during CPR Andrey Drobyshev
2026-06-26 16:46 ` [PATCH v3 3/7] vhost-vsock: fix FD leak in realize() Andrey Drobyshev
2026-06-26 16:46 ` [PATCH v3 4/7] vhost-vsock: preserve vhost FD during CPR Andrey Drobyshev
2026-08-18 15:29 ` Stefano Garzarella
2026-08-19 14:38 ` Andrey Drobyshev
2026-08-19 15:11 ` Michael S. Tsirkin
2026-08-19 15:22 ` Andrey Drobyshev
2026-08-19 18:53 ` Michael S. Tsirkin
2026-06-26 16:46 ` [PATCH v3 5/7] vhost: factor out vhost_dev_init_backend() Andrey Drobyshev
2026-08-18 15:29 ` Stefano Garzarella
2026-08-19 14:38 ` Andrey Drobyshev
2026-06-26 16:46 ` [PATCH v3 6/7] vhost: add vhost_dev_set_owner() / vhost_dev_reset_owner() helpers Andrey Drobyshev
2026-06-26 16:46 ` [PATCH v3 7/7] vhost-vsock: hand off device ownership across CPR Andrey Drobyshev
2026-08-18 15:30 ` Stefano Garzarella
2026-08-19 14:38 ` Andrey Drobyshev
2026-06-30 18:35 ` [PATCH v3 0/7] migration/cpr: support vhost-vsock devices Maciej S. Szmigiero
2026-08-11 14:12 ` Andrey Drobyshev
2026-08-18 11:02 ` Andrey Drobyshev [this message]
2026-08-18 15:33 ` Stefano Garzarella
2026-08-19 14:39 ` Andrey Drobyshev
2026-07-14 16:03 ` Vladimir Sementsov-Ogievskiy
2026-07-15 10:25 ` Andrey Drobyshev
2026-07-15 10:48 ` Vladimir Sementsov-Ogievskiy
2026-07-15 12:11 ` Andrey Drobyshev
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=dadd79c2-89c7-405a-b2c9-7973c3fe62d1@virtuozzo.com \
--to=andrey.drobyshev@virtuozzo.com \
--cc=bchaney@akamai.com \
--cc=den@openvz.org \
--cc=dongli.zhang@oracle.com \
--cc=farosas@suse.de \
--cc=mail@maciej.szmigiero.name \
--cc=mark.kanda@oracle.com \
--cc=mst@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.