summaryrefslogtreecommitdiff
path: root/vl.c
diff options
context:
space:
mode:
authorPaolo Bonzini <pbonzini@redhat.com>2013-01-25 14:12:37 +0100
committerAnthony Liguori <aliguori@us.ibm.com>2013-02-01 15:53:11 -0600
commitb09995aef1d4a5879000a196a82e37b0511c8e03 (patch)
tree5e9019b61486cb07a7707633f209fa630863dc7d /vl.c
parentdc7389b79a15082fa4824bd3de966499f3b8cb2a (diff)
downloadqemu-b09995aef1d4a5879000a196a82e37b0511c8e03.tar.gz
qemu-b09995aef1d4a5879000a196a82e37b0511c8e03.tar.bz2
qemu-b09995aef1d4a5879000a196a82e37b0511c8e03.zip
qdev: drop extra references at creation time
qdev_free and qbus_free have to do unparent+unref, because nobody else drops the initial reference (the one included by object_initialize) before them. For device_init_func and do_device_add, this is trivially correct, since the DeviceState goes out of scope. For qdev_create, qdev_try_create and qbus_init, it is a bit more tricky. What we are doing here is just assuming that the caller knows what it's doing, and won't call qdev_free/qbus_free while the device is still there. This is a pretty reasonable assumption and (behind the scenes) is also what GObject/GTK does. GTK actually has a "floating reference" that goes away as soon as the caller does gtk_container_add or something like that, but in the end qbus_init and qdev_try_create are already adding the new object to its qdev parent! So in the end the two solutions are the same. Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Diffstat (limited to 'vl.c')
-rw-r--r--vl.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/vl.c b/vl.c
index f094f04a2c..315598994f 100644
--- a/vl.c
+++ b/vl.c
@@ -2236,6 +2236,7 @@ static int device_init_func(QemuOpts *opts, void *opaque)
dev = qdev_device_add(opts);
if (!dev)
return -1;
+ object_unref(OBJECT(dev));
return 0;
}