From: Lin Ma <lma@suse.com>
To: mst@redhat.com, "kraxel@redhat.com >> Gerd Hoffmann" <kraxel@redhat.com>
Cc: "qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>
Subject: [Qemu-devel] [RFC PATCH] Fix hotplug/hotunplug issue about virtio 1.0 devices
Date: Mon, 20 Jul 2015 23:14:58 +0800 [thread overview]
Message-ID: <55AD1072.7030706@suse.com> (raw)
Hi Michael and Gerd,
I found an hotplug/hotunplug issue about virtio 1.0 devices and trying
to fix it.
The bug description is:
(qemu) device_add virtio-gpu-pci,id=gpu0
(qemu) device_del gpu0
(qemu) device_add virtio-gpu-pci,id=gpu0
Duplicate ID 'gpu0' for device
Try "help device_add" for more information
My fix looks like this:
diff --git a/hw/virtio/virtio-pci.c b/hw/virtio/virtio-pci.c
index 283401a..098fc83 100644
--- a/hw/virtio/virtio-pci.c
+++ b/hw/virtio/virtio-pci.c
@@ -1413,6 +1413,12 @@ static void
virtio_pci_modern_region_map(VirtIOPCIProxy *proxy,
virtio_pci_add_mem_cap(proxy, cap);
}
+static void virtio_pci_modern_region_unmap(VirtIOPCIProxy *proxy,
+ VirtIOPCIRegion *region)
+{
+ memory_region_del_subregion(&proxy->modern_bar, ®ion->mr);
+}
+
/* This is called by virtio-bus just after the device is plugged. */
static void virtio_pci_device_plugged(DeviceState *d, Error **errp)
{
@@ -1584,6 +1590,16 @@ static void virtio_pci_exit(PCIDevice *pci_dev)
msix_uninit_exclusive_bar(pci_dev);
address_space_destroy(&proxy->modern_as);
+ object_unparent(OBJECT(&proxy->modern_cfg));
+
+ bool modern = !(proxy->flags & VIRTIO_PCI_FLAG_DISABLE_MODERN);
+ if (modern) {
+ virtio_pci_modern_region_unmap(proxy, &proxy->common);
+ virtio_pci_modern_region_unmap(proxy, &proxy->isr);
+ virtio_pci_modern_region_unmap(proxy, &proxy->device);
+ virtio_pci_modern_region_unmap(proxy, &proxy->notify);
+ }
+ memory_region_unref(&proxy->modern_bar);
}
static void virtio_pci_reset(DeviceState *qdev)
But after applying the fix, I got the following errors:
(qemu) device_add virtio-gpu-pci,id=gpu0
(qemu) device_del gpu0
(qemu) **
ERROR:qom/object.c:825:object_unref: assertion failed: (obj->ref > 0)
......
I think because of the grace period of rcu, the function
memory_region_unref(as->root) in do_address_space_destroy isn't
performed immediately,
The do_address_space_destroy is always performed after virtio_pci_exit,
That caused 'assertion failed: (obj->ref > 0)'.
I have no idea whether my guess is correct or in correct, and don't know
how to avoid this assertion failure in this situation.
Does my fix make sense ? May I have your ideas or suggestions?
Thanks!
Lin
next reply other threads:[~2015-07-20 15:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-20 15:14 Lin Ma [this message]
2015-07-20 15:36 ` [Qemu-devel] [RFC PATCH] Fix hotplug/hotunplug issue about virtio 1.0 devices Michael S. Tsirkin
2015-07-21 5:37 ` Lin Ma
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=55AD1072.7030706@suse.com \
--to=lma@suse.com \
--cc=kraxel@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
/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.