From: Jens Freimann <jfreimann@redhat.com>
To: qemu-devel@nongnu.org
Cc: berrange@redhat.com, ehabkost@redhat.com, mst@redhat.com,
aadam@redhat.com, jasowang@redhat.com, quintela@redhat.com,
dgilbert@redhat.com, armbru@redhat.com,
alex.williamson@redhat.com, laine@redhat.com,
pbonzini@redhat.com, ailan@redhat.com, parav@mellanox.com
Subject: [PATCH v7 04/11] pci: mark device having guest unplug request pending
Date: Tue, 29 Oct 2019 12:48:58 +0100 [thread overview]
Message-ID: <20191029114905.6856-5-jfreimann@redhat.com> (raw)
In-Reply-To: <20191029114905.6856-1-jfreimann@redhat.com>
Set pending_deleted_event in DeviceState for failover
primary devices that were successfully unplugged by the Guest OS.
Signed-off-by: Jens Freimann <jfreimann@redhat.com>
---
hw/pci/pcie.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/hw/pci/pcie.c b/hw/pci/pcie.c
index 19363ff8ce..08718188bb 100644
--- a/hw/pci/pcie.c
+++ b/hw/pci/pcie.c
@@ -457,6 +457,7 @@ static void pcie_unplug_device(PCIBus *bus, PCIDevice *dev, void *opaque)
HotplugHandler *hotplug_ctrl = qdev_get_hotplug_handler(DEVICE(dev));
if (dev->partially_hotplugged) {
+ dev->qdev.pending_deleted_event = false;
return;
}
hotplug_handler_unplug(hotplug_ctrl, DEVICE(dev), &error_abort);
@@ -476,6 +477,8 @@ void pcie_cap_slot_unplug_request_cb(HotplugHandler *hotplug_dev,
return;
}
+ dev->pending_deleted_event = true;
+
/* In case user cancel the operation of multi-function hot-add,
* remove the function that is unexposed to guest individually,
* without interaction with guest.
--
2.21.0
next prev parent reply other threads:[~2019-10-29 11:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-29 11:48 [PATCH v7 0/11] add failover feature for assigned network devices Jens Freimann
2019-10-29 11:48 ` [PATCH v7 01/11] qdev/qbus: add hidden device support Jens Freimann
2019-10-29 11:48 ` [PATCH v7 02/11] pci: add option for net failover Jens Freimann
2019-10-29 11:48 ` [PATCH v7 03/11] pci: mark devices partially unplugged Jens Freimann
2019-10-29 11:48 ` Jens Freimann [this message]
2019-10-29 11:48 ` [PATCH v7 05/11] qapi: add unplug primary event Jens Freimann
2019-10-29 12:50 ` Markus Armbruster
2019-10-29 13:46 ` Jens Freimann
2019-10-29 14:05 ` Markus Armbruster
2019-10-29 11:49 ` [PATCH v7 06/11] qapi: add failover negotiated event Jens Freimann
2019-10-29 12:47 ` Markus Armbruster
2019-10-29 11:49 ` [PATCH v7 07/11] migration: allow unplug during migration for failover devices Jens Freimann
2019-10-29 11:49 ` [PATCH v7 08/11] migration: add new migration state wait-unplug Jens Freimann
2019-10-29 11:49 ` [PATCH v7 09/11] libqos: tolerate wait-unplug migration state Jens Freimann
2019-10-29 11:49 ` [PATCH v7 10/11] net/virtio: add failover support Jens Freimann
2019-10-29 11:49 ` [PATCH v7 11/11] vfio: unplug failover primary device before migration Jens Freimann
2019-11-04 21:21 ` [PATCH v7 0/11] add failover feature for assigned network devices Parav Pandit
2019-11-04 22:09 ` Laine Stump
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=20191029114905.6856-5-jfreimann@redhat.com \
--to=jfreimann@redhat.com \
--cc=aadam@redhat.com \
--cc=ailan@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=ehabkost@redhat.com \
--cc=jasowang@redhat.com \
--cc=laine@redhat.com \
--cc=mst@redhat.com \
--cc=parav@mellanox.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).