cryptospore / rpms / qemu-kvm

Forked from rpms/qemu-kvm 2 years ago
Clone

Blame SOURCES/kvm-qdev-Document-that-pointer-properties-kill-device_ad.patch

0a122b
From 695e02fdf90a0487f70b26b276e71e0924a817dc Mon Sep 17 00:00:00 2001
0a122b
From: Markus Armbruster <armbru@redhat.com>
0a122b
Date: Thu, 16 Jan 2014 15:25:19 -0500
0a122b
Subject: [PATCH 13/14] qdev: Document that pointer properties kill device_add
0a122b
MIME-Version: 1.0
0a122b
Content-Type: text/plain; charset=UTF-8
0a122b
Content-Transfer-Encoding: 8bit
0a122b
0a122b
Message-id: <1389885919-16158-3-git-send-email-armbru@redhat.com>
0a122b
Patchwork-id: 56749
0a122b
O-Subject: [PATCH 7.0 qemu-kvm 2/2] qdev: Document that pointer properties kill device_add
0a122b
Bugzilla: 1031098
0a122b
RH-Acked-by: Paolo Bonzini <pbonzini@redhat.com>
0a122b
RH-Acked-by: Laszlo Ersek <lersek@redhat.com>
0a122b
RH-Acked-by: Miroslav Rezanina <mrezanin@redhat.com>
0a122b
0a122b
Ask users of DEFINE_PROP_PTR() to set
0a122b
cannot_instantiate_with_device_add_yet, or explain why it's not
0a122b
needed.
0a122b
0a122b
Signed-off-by: Markus Armbruster <armbru@redhat.com>
0a122b
Signed-off-by: Andreas Färber <afaerber@suse.de>
0a122b
(cherry picked from commit c272758f93b9c88c884461a2baa37b8f4008bf02)
0a122b
---
0a122b
 include/hw/qdev-properties.h | 17 +++++++++++++++++
0a122b
 1 file changed, 17 insertions(+)
0a122b
0a122b
Signed-off-by: Miroslav Rezanina <mrezanin@redhat.com>
0a122b
---
0a122b
 include/hw/qdev-properties.h | 17 +++++++++++++++++
0a122b
 1 file changed, 17 insertions(+)
0a122b
0a122b
diff --git a/include/hw/qdev-properties.h b/include/hw/qdev-properties.h
0a122b
index 692f82e..77c6f7c 100644
0a122b
--- a/include/hw/qdev-properties.h
0a122b
+++ b/include/hw/qdev-properties.h
0a122b
@@ -122,8 +122,25 @@ extern PropertyInfo qdev_prop_arraylen;
0a122b
 #define DEFINE_PROP_PCI_DEVFN(_n, _s, _f, _d)                   \
0a122b
     DEFINE_PROP_DEFAULT(_n, _s, _f, _d, qdev_prop_pci_devfn, int32_t)
0a122b
 
0a122b
+/*
0a122b
+ * Please avoid pointer properties.  If you must use them, you must
0a122b
+ * cover them in their device's class init function as follows:
0a122b
+ *
0a122b
+ * - If the property must be set, the device cannot be used with
0a122b
+ *   device_add, so add code like this:
0a122b
+ *   |* Reason: pointer property "NAME-OF-YOUR-PROP" *|
0a122b
+ *   DeviceClass *dc = DEVICE_CLASS(class);
0a122b
+ *   dc->cannot_instantiate_with_device_add_yet = true;
0a122b
+ *
0a122b
+ * - If the property may safely remain null, document it like this:
0a122b
+ *   |*
0a122b
+ *    * Note: pointer property "interrupt_vector" may remain null, thus
0a122b
+ *    * no need for dc->cannot_instantiate_with_device_add_yet = true;
0a122b
+ *    *|
0a122b
+ */
0a122b
 #define DEFINE_PROP_PTR(_n, _s, _f)             \
0a122b
     DEFINE_PROP(_n, _s, _f, qdev_prop_ptr, void*)
0a122b
+
0a122b
 #define DEFINE_PROP_CHR(_n, _s, _f)             \
0a122b
     DEFINE_PROP(_n, _s, _f, qdev_prop_chr, CharDriverState*)
0a122b
 #define DEFINE_PROP_STRING(_n, _s, _f)             \
0a122b
-- 
0a122b
1.8.3.1
0a122b