Hi all!

That the second part of virtio-net backend transfer feature,
following previous
 "[PATCH v9 0/7] net/tap: simple refactoring".

Here we realize postponing TAP opening to some future
point, when we know, are we going to do backend-transfer
incoming migration (and get open fd from migration stream),
or we should do open().

v9:
most of patches just picked from
 "[PATCH v9 0/7] net/tap: simple refactoring".
but, 01 is new, and 09 is significantly changed:
instead of hacking with .check_peer_type and detecting
virtio-net by name, use the approach like in parallel
series for chardev:
 "[PATCH v4 0/7] chardev: postpone connect":
introduce specific PROPERTY macro, and avoid connecting
in setter of "netdev" property.

Final part of virtio-net backend transfer is coming
soon and will be based on this series.

Based-on: <[email protected]>

Vladimir Sementsov-Ogievskiy (9):
  net: introduce backend-connect concept
  net/tap: rework net_tap_init()
  net/tap: split net_tap_fd_init()
  net/tap: rework sndbuf handling
  net/tap: introduce net_tap_setup()
  net/tap: move vhost fd initialization to net_tap_new()
  net/tap: finalize net_tap_set_fd() logic
  net/tap: introduce TAP_IFNAME_SZ
  net/tap: postpone tap setup to net_backend_connect() call

 hw/core/qdev-properties-system.c    |  29 ++-
 include/hw/qdev-properties-system.h |   2 +
 include/net/net.h                   |   6 +
 net/net.c                           |  15 ++
 net/tap.c                           | 283 +++++++++++++++++++++-------
 5 files changed, 264 insertions(+), 71 deletions(-)

-- 
2.48.1


Reply via email to