qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Vivier <lvivier@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
	"Eduardo Habkost" <ehabkost@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	"Jason Wang" <jasowang@redhat.com>,
	"Juan Quintela" <quintela@redhat.com>,
	"Alex Williamson" <alex.williamson@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Jens Freimann" <jfreimann@redhat.com>
Subject: [RFC PATCH 0/6] virtio-net failover cleanup and new features
Date: Mon, 16 Aug 2021 16:58:18 +0200	[thread overview]
Message-ID: <20210816145824.15825-1-lvivier@redhat.com> (raw)

This series moves the code used by virtio-net failover from the
virtio-net device to the PCI subsystem.

Doing that, we can use failover with a regular QEMU PCI device
(we can add the function call to unregister the ROM vmstate) and we
can also use this code to unplug a PCI card before migration
and plug it back after migration without using a failover
device (of course, connectivity is lost during all the migration).
In contrary of failover, this does not need support from the
guest system to work.

Laurent Vivier (6):
  qdev: add an Error parameter to the DeviceListener hide_device()
    function
  qdev/qbus: remove failover specific code
  failover: virtio-net: remove failover_primary_hidden flag
  failover: pci: move failover hotplug/unplug code into pci subsystem
  failover: pci: unregister ROM on unplug
  pci: automatically unplug a PCI card before migration

 include/hw/pci/pci.h           |   5 +
 include/hw/qdev-core.h         |   6 +-
 include/hw/virtio/virtio-net.h |   4 -
 include/hw/virtio/virtio.h     |   1 -
 hw/core/qdev.c                 |   4 +-
 hw/net/virtio-net.c            | 144 -------------------
 hw/pci/pci.c                   | 245 +++++++++++++++++++++++++++++++--
 hw/vfio/pci.c                  |   2 +-
 softmmu/qdev-monitor.c         |  14 +-
 9 files changed, 252 insertions(+), 173 deletions(-)

-- 
2.31.1




             reply	other threads:[~2021-08-16 15:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-16 14:58 Laurent Vivier [this message]
2021-08-16 14:58 ` [RFC PATCH 1/6] qdev: add an Error parameter to the DeviceListener hide_device() function Laurent Vivier
2021-08-16 14:58 ` [RFC PATCH 2/6] qdev/qbus: remove failover specific code Laurent Vivier
2021-08-16 14:58 ` [RFC PATCH 3/6] failover: virtio-net: remove failover_primary_hidden flag Laurent Vivier
2021-08-16 14:58 ` [RFC PATCH 4/6] failover: pci: move failover hotplug/unplug code into pci subsystem Laurent Vivier
2021-08-16 14:58 ` [RFC PATCH 5/6] failover: pci: unregister ROM on unplug Laurent Vivier
2021-08-16 14:58 ` [RFC PATCH 6/6] pci: automatically unplug a PCI card before migration Laurent Vivier

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=20210816145824.15825-1-lvivier@redhat.com \
    --to=lvivier@redhat.com \
    --cc=alex.williamson@redhat.com \
    --cc=berrange@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=jfreimann@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@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 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).