From: Markus Armbruster <armbru@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>
Cc: mst@redhat.com, jasowang@redhat.com, pbonzini@redhat.com,
berrange@redhat.com, eduardo@habkost.net, peterx@redhat.com,
farosas@suse.de, eblake@redhat.com, thuth@redhat.com,
philmd@linaro.org, zhao1.liu@intel.com, qemu-devel@nongnu.org,
leiyang@redhat.com, davydov-max@yandex-team.ru,
yc-core@yandex-team.ru, raphael.s.norwitz@gmail.com
Subject: Re: [PATCH v9 2/8] qapi: introduce query-backend-transfer-support
Date: Fri, 07 Nov 2025 06:28:44 +0100 [thread overview]
Message-ID: <87cy5ue7hv.fsf@pond.sub.org> (raw)
In-Reply-To: <75cd160f-2f70-4522-aaa0-6e8a2a3b7c01@yandex-team.ru> (Vladimir Sementsov-Ogievskiy's message of "Thu, 6 Nov 2025 22:27:36 +0300")
Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru> writes:
> On 06.11.25 18:30, Markus Armbruster wrote:
>> Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru> writes:
>>
>>> We are going to implement backend-transfer feature: some devices
>>> will be able to transfer their backend through migration stream
>>> for local migration through UNIX domain socket. For example,
>>> virtio-net will migrate its attached TAP netdev, with all its
>>> connected file descriptors.
>>>
>>> Let's add a command to list supporting devices (no one for now),
>>> together with necessary infrastructure in qdev code.
>>
>> Use case?
>
> Will add:
>
> With this command management tool can query such lists on source and
> target, and get intersection of them, to now the set of devices, for
> which we can enable backend-transfer for given source and target QEMUs.
I like it. Would it make sense to add something similar to QAPI schema
doc comments?
[...]
next prev parent reply other threads:[~2025-11-07 5:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 20:31 [PATCH v9 0/8] virtio-net: live-TAP local migration Vladimir Sementsov-Ogievskiy
2025-10-30 20:31 ` [PATCH v9 1/8] migration: introduce .pre_incoming() vmsd handler Vladimir Sementsov-Ogievskiy
2025-10-30 20:31 ` [PATCH v9 2/8] qapi: introduce query-backend-transfer-support Vladimir Sementsov-Ogievskiy
2025-11-06 15:30 ` Markus Armbruster
2025-11-06 19:27 ` Vladimir Sementsov-Ogievskiy
2025-11-07 5:28 ` Markus Armbruster [this message]
2025-11-07 6:09 ` Vladimir Sementsov-Ogievskiy
2025-10-30 20:31 ` [PATCH v9 3/8] qapi: add backend-transfer migration parameter Vladimir Sementsov-Ogievskiy
2025-11-06 15:44 ` Markus Armbruster
2025-10-30 20:31 ` [PATCH v9 4/8] net: introduce vmstate_net_peer_backend Vladimir Sementsov-Ogievskiy
2025-10-30 20:31 ` [PATCH v9 5/8] virtio-net: support backend-transfer migration Vladimir Sementsov-Ogievskiy
2025-10-30 20:31 ` [PATCH v9 6/8] net/tap: " Vladimir Sementsov-Ogievskiy
2025-10-30 20:31 ` [PATCH v9 7/8] tests/functional: add skipWithoutSudo() decorator Vladimir Sementsov-Ogievskiy
2025-10-30 20:31 ` [PATCH v9 8/8] tests/functional: add test_tap_migration Vladimir Sementsov-Ogievskiy
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=87cy5ue7hv.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=davydov-max@yandex-team.ru \
--cc=eblake@redhat.com \
--cc=eduardo@habkost.net \
--cc=farosas@suse.de \
--cc=jasowang@redhat.com \
--cc=leiyang@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=raphael.s.norwitz@gmail.com \
--cc=thuth@redhat.com \
--cc=vsementsov@yandex-team.ru \
--cc=yc-core@yandex-team.ru \
--cc=zhao1.liu@intel.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.