qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>
Cc: Peter Xu <peterx@redhat.com>,
	mst@redhat.com, jasowang@redhat.com, farosas@suse.de,
	sw@weilnetz.de, eblake@redhat.com, armbru@redhat.com,
	thuth@redhat.com, philmd@linaro.org, qemu-devel@nongnu.org,
	michael.roth@amd.com, steven.sistare@oracle.com,
	leiyang@redhat.com, davydov-max@yandex-team.ru,
	yc-core@yandex-team.ru, raphael.s.norwitz@gmail.com
Subject: Re: [PATCH v7 16/19] qapi: add interface for backend-transfer virtio-net/tap migration
Date: Wed, 15 Oct 2025 08:11:33 +0100	[thread overview]
Message-ID: <aO9JEAPY9c3gtYvs@redhat.com> (raw)
In-Reply-To: <5b9a466f-19c2-41a0-86b0-aa8ce7c98443@yandex-team.ru>

On Wed, Oct 15, 2025 at 12:54:21AM +0300, Vladimir Sementsov-Ogievskiy wrote:
> On 15.10.25 00:46, Vladimir Sementsov-Ogievskiy wrote:
> > > 
> > > And then, developing similar migration for vhost-user-blk, found
> > > that I can't use on boolean capability for such features, the reason
> > > in commit message, which we discuss now.
> > 
> > Why a bool isn't enough?  Could you share a link to that discussion?
> 
> I mean, one boolean is not enough for different devices, when not assisted
> by per-device options. So, I came to idea of "list of backend targets"
> in migration parameter.

If we need to identify backends or frontends, surely we should be using
the "id" that the mgmt app used when creating the object, that gets set
in the QOM tree.

With regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  reply	other threads:[~2025-10-15  7:13 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-10 17:39 [PATCH v7 00/19] virtio-net: live-TAP local migration Vladimir Sementsov-Ogievskiy
2025-10-10 17:39 ` [PATCH v7 01/19] net/tap: net_init_tap_one(): drop extra error propagation Vladimir Sementsov-Ogievskiy
2025-10-10 17:39 ` [PATCH v7 02/19] net/tap: net_init_tap_one(): move parameter checking earlier Vladimir Sementsov-Ogievskiy
2025-10-10 17:39 ` [PATCH v7 03/19] net/tap: rework net_tap_init() Vladimir Sementsov-Ogievskiy
2025-10-10 17:39 ` [PATCH v7 04/19] net/tap: pass NULL to net_init_tap_one() in cases when scripts are NULL Vladimir Sementsov-Ogievskiy
2025-10-10 17:39 ` [PATCH v7 05/19] net/tap: rework scripts handling Vladimir Sementsov-Ogievskiy
2025-10-10 17:39 ` [PATCH v7 06/19] net/tap: setup exit notifier only when needed Vladimir Sementsov-Ogievskiy
2025-10-10 17:39 ` [PATCH v7 07/19] net/tap: split net_tap_fd_init() Vladimir Sementsov-Ogievskiy
2025-10-10 17:39 ` [PATCH v7 08/19] net/tap: tap_set_sndbuf(): add return value Vladimir Sementsov-Ogievskiy
2025-10-10 17:39 ` [PATCH v7 09/19] net/tap: rework tap_set_sndbuf() Vladimir Sementsov-Ogievskiy
2025-10-10 17:39 ` [PATCH v7 10/19] net/tap: rework sndbuf handling Vladimir Sementsov-Ogievskiy
2025-10-10 17:39 ` [PATCH v7 11/19] net/tap: introduce net_tap_setup() Vladimir Sementsov-Ogievskiy
2025-10-10 17:39 ` [PATCH v7 12/19] net/tap: move vhost fd initialization to net_tap_new() Vladimir Sementsov-Ogievskiy
2025-10-10 17:39 ` [PATCH v7 13/19] net/tap: finalize net_tap_set_fd() logic Vladimir Sementsov-Ogievskiy
2025-10-10 17:39 ` [PATCH v7 14/19] migration: introduce .pre_incoming() vmsd handler Vladimir Sementsov-Ogievskiy
2025-10-14 16:26   ` Peter Xu
2025-10-10 17:39 ` [PATCH v7 15/19] net/tap: postpone tap setup to pre-incoming Vladimir Sementsov-Ogievskiy
2025-10-10 17:39 ` [PATCH v7 16/19] qapi: add interface for backend-transfer virtio-net/tap migration Vladimir Sementsov-Ogievskiy
2025-10-14 16:33   ` Peter Xu
2025-10-14 19:31     ` Vladimir Sementsov-Ogievskiy
2025-10-14 20:25       ` Peter Xu
2025-10-14 21:46         ` Vladimir Sementsov-Ogievskiy
2025-10-14 21:54           ` Vladimir Sementsov-Ogievskiy
2025-10-15  7:11             ` Daniel P. Berrangé [this message]
2025-10-15 18:27           ` Peter Xu
2025-10-15 20:17             ` Vladimir Sementsov-Ogievskiy
2025-10-16 16:25               ` Peter Xu
2025-10-16 17:06                 ` Vladimir Sementsov-Ogievskiy
2025-10-10 17:39 ` [PATCH v7 17/19] virtio-net: support backend-transfer migration for virtio-net/tap Vladimir Sementsov-Ogievskiy
2025-10-10 17:39 ` [PATCH v7 18/19] tests/functional: add skipWithoutSudo() decorator Vladimir Sementsov-Ogievskiy
2025-10-10 17:39 ` [PATCH v7 19/19] tests/functional: add test_x86_64_tap_migration Vladimir Sementsov-Ogievskiy
2025-10-11 15:26 ` [PATCH v7 00/19] virtio-net: live-TAP local migration Lei Yang

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=aO9JEAPY9c3gtYvs@redhat.com \
    --to=berrange@redhat.com \
    --cc=armbru@redhat.com \
    --cc=davydov-max@yandex-team.ru \
    --cc=eblake@redhat.com \
    --cc=farosas@suse.de \
    --cc=jasowang@redhat.com \
    --cc=leiyang@redhat.com \
    --cc=michael.roth@amd.com \
    --cc=mst@redhat.com \
    --cc=peterx@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=raphael.s.norwitz@gmail.com \
    --cc=steven.sistare@oracle.com \
    --cc=sw@weilnetz.de \
    --cc=thuth@redhat.com \
    --cc=vsementsov@yandex-team.ru \
    --cc=yc-core@yandex-team.ru \
    /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 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 NNTP newsgroup(s).