From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel@nongnu.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Eduardo Habkost" <eduardo@habkost.net>,
"Viresh Kumar" <viresh.kumar@linaro.org>,
"Mathieu Poirier" <mathieu.poirier@linaro.org>,
"Gonglei (Arei)" <arei.gonglei@huawei.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Erik Schilling" <erik.schilling@linaro.org>,
"Jason Wang" <jasowang@redhat.com>,
"Mark Cave-Ayland" <mark.cave-ayland@ilande.co.uk>,
"Gerd Hoffmann" <kraxel@redhat.com>,
virtio-fs@redhat.com,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Eric Blake" <eblake@redhat.com>
Subject: [PATCH v2 02/13] include/hw: document the device_class_set_parent_* fns
Date: Tue, 18 Apr 2023 17:21:29 +0100 [thread overview]
Message-ID: <20230418162140.373219-3-alex.bennee@linaro.org> (raw)
In-Reply-To: <20230418162140.373219-1-alex.bennee@linaro.org>
These are useful functions for when you want proper inheritance of
functionality across realize/unrealize calls.
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
---
include/hw/qdev-core.h | 27 +++++++++++++++++++++++++++
1 file changed, 27 insertions(+)
diff --git a/include/hw/qdev-core.h b/include/hw/qdev-core.h
index d4bbc30c92..b1d194b561 100644
--- a/include/hw/qdev-core.h
+++ b/include/hw/qdev-core.h
@@ -795,9 +795,36 @@ void device_class_set_props(DeviceClass *dc, Property *props);
void device_class_set_parent_reset(DeviceClass *dc,
DeviceReset dev_reset,
DeviceReset *parent_reset);
+
+/**
+ * device_class_set_parent_realize(): set up for chaining realize fns
+ * @dc: The device class
+ * @dev_realize: the device realize function
+ * @parent_realize: somewhere to save the parents realize function
+ *
+ * This is intended to be used when the new realize function will
+ * eventually call its parent realization function during creation.
+ * This requires storing the function call somewhere (usually in the
+ * instance structure) so you can eventually call:
+ * my_dev->parent_realize(dev, errp);
+ */
void device_class_set_parent_realize(DeviceClass *dc,
DeviceRealize dev_realize,
DeviceRealize *parent_realize);
+
+
+/**
+ * device_class_set_parent_unrealize(): set up for chaining unrealize fns
+ * @dc: The device class
+ * @dev_unrealize: the device realize function
+ * @parent_unrealize: somewhere to save the parents unrealize function
+ *
+ * This is intended to be used when the new unrealize function will
+ * eventually call its parent unrealization function during the
+ * unrealize phase. This requires storing the function call somewhere
+ * (usually in the instance structure) so you can eventually call:
+ * my_dev->parent_unrealize(dev);
+ */
void device_class_set_parent_unrealize(DeviceClass *dc,
DeviceUnrealize dev_unrealize,
DeviceUnrealize *parent_unrealize);
--
2.39.2
next prev parent reply other threads:[~2023-04-18 16:23 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 16:21 [PATCH v2 00/13] virtio: add vhost-user-generic and reduce copy and paste Alex Bennée
2023-04-18 16:21 ` [PATCH v2 01/13] include: attempt to document device_class_set_props Alex Bennée
2023-04-20 9:21 ` Mark Cave-Ayland
2023-05-23 20:30 ` Stefan Hajnoczi
2023-04-18 16:21 ` Alex Bennée [this message]
2023-04-20 9:24 ` [PATCH v2 02/13] include/hw: document the device_class_set_parent_* fns Mark Cave-Ayland
2023-04-18 16:21 ` [PATCH v2 03/13] hw/virtio: fix typo in VIRTIO_CONFIG_IRQ_IDX comments Alex Bennée
2023-04-20 9:25 ` Mark Cave-Ayland
2023-05-23 20:35 ` Stefan Hajnoczi
2023-04-18 16:21 ` [PATCH v2 04/13] include/hw/virtio: document virtio_notify_config Alex Bennée
2023-04-20 9:27 ` Mark Cave-Ayland
2023-05-23 20:40 ` Stefan Hajnoczi
2023-04-18 16:21 ` [PATCH v2 05/13] include/hw/virtio: add kerneldoc for virtio_init Alex Bennée
2023-04-20 9:29 ` Mark Cave-Ayland
2023-05-23 20:41 ` Stefan Hajnoczi
2023-04-18 16:21 ` [PATCH v2 06/13] include/hw/virtio: document some more usage of notifiers Alex Bennée
2023-04-20 9:32 ` Mark Cave-Ayland
2023-05-23 20:52 ` Stefan Hajnoczi
2023-04-18 16:21 ` [PATCH v2 07/13] virtio: add vhost-user-base and a generic vhost-user-device Alex Bennée
2023-04-20 9:47 ` Mark Cave-Ayland
2023-04-18 16:21 ` [PATCH v2 08/13] virtio: add PCI stub for vhost-user-device Alex Bennée
2023-04-20 9:54 ` Mark Cave-Ayland
2023-04-18 16:21 ` [PATCH v2 09/13] hw/virtio: derive vhost-user-rng from vhost-user-device Alex Bennée
2023-04-20 10:09 ` Mark Cave-Ayland
2023-04-18 16:21 ` [PATCH v2 10/13] hw/virtio: add config support to vhost-user-device Alex Bennée
2023-04-18 16:21 ` [PATCH v2 11/13] hw/virtio: derive vhost-user-gpio from vhost-user-device Alex Bennée
2023-04-20 10:12 ` Mark Cave-Ayland
2023-04-18 16:21 ` [PATCH v2 12/13] hw/virtio: derive vhost-user-i2c from vhost-user-base Alex Bennée
2023-04-20 10:18 ` Mark Cave-Ayland
2023-04-18 16:21 ` [PATCH v2 13/13] docs/system: add a basic enumeration of vhost-user devices Alex Bennée
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=20230418162140.373219-3-alex.bennee@linaro.org \
--to=alex.bennee@linaro.org \
--cc=arei.gonglei@huawei.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=eduardo@habkost.net \
--cc=erik.schilling@linaro.org \
--cc=jasowang@redhat.com \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=mathieu.poirier@linaro.org \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=viresh.kumar@linaro.org \
--cc=virtio-fs@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).