From: Eduardo Habkost <ehabkost@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Markus Armbruster" <armbru@redhat.com>
Subject: [Qemu-devel] [RFC 0/3] qom/qdev: Try to clarify ownership rules
Date: Thu, 12 Jul 2018 16:45:19 -0300 [thread overview]
Message-ID: <20180712194522.31063-1-ehabkost@redhat.com> (raw)
The ownership rules of some QOM and qdev functions are not very
clear. Some of the rules are not trivial because they depend
on other arguments or flags specified when a property was
created.
This is an attempt to clarify the existing ownership rules of
those functions to avoid confusion in the future.
Eduardo Habkost (3):
qom: Document reference count ownership rules
qdev: Document ownership rules of qbus_create*()
pci: Document ownership rules of pci_root_bus_new*()
include/hw/pci/pci.h | 15 +++++++++
include/hw/qdev-core.h | 24 ++++++++++++++
include/qom/object.h | 73 ++++++++++++++++++++++++------------------
hw/core/bus.c | 5 +++
4 files changed, 86 insertions(+), 31 deletions(-)
--
2.18.0.rc1.1.g3f1ff2140
next reply other threads:[~2018-07-12 19:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-12 19:45 Eduardo Habkost [this message]
2018-07-12 19:45 ` [Qemu-devel] [RFC 1/3] qom: Document reference count ownership rules Eduardo Habkost
2018-07-13 9:07 ` Thomas Huth
2018-07-13 20:20 ` Eduardo Habkost
2018-07-12 19:45 ` [Qemu-devel] [RFC 2/3] qdev: Document ownership rules of qbus_create*() Eduardo Habkost
2018-07-16 10:34 ` Marcel Apfelbaum
2018-07-12 19:45 ` [Qemu-devel] [RFC 3/3] pci: Document ownership rules of pci_root_bus_new*() Eduardo Habkost
2018-07-16 10:33 ` Marcel Apfelbaum
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=20180712194522.31063-1-ehabkost@redhat.com \
--to=ehabkost@redhat.com \
--cc=armbru@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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).