From: "Daniel P. Berrange" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Pavel Fedin" <p.fedin@samsung.com>, "Andreas Färber" <afaerber@suse.de>
Subject: [Qemu-devel] [PATCH v3 0/5] qom: more efficient object property handling
Date: Thu, 8 Oct 2015 15:08:59 +0100 [thread overview]
Message-ID: <1444313344-16196-1-git-send-email-berrange@redhat.com> (raw)
This patch series is a combination of my own previous patch to
add support for object properties against classes:
https://lists.gnu.org/archive/html/qemu-devel/2015-09/msg05953.html
And Pavel Fedin's patch to use a hash table instead of list
https://lists.gnu.org/archive/html/qemu-devel/2015-10/msg01455.html
I pulled Pavel's patch in to my series, since both our patches
touch the same code and thus generate nasty merge conflicts.
In resolving these conflicts I decided we needed a new helper
method object_property_foreach to deal with iteration over
properties, hence we now have a short series of patches.
I made a few changes to Pavel's patch but the guts of it are
still his work, so I left him as GIT author, but removed his
Signed-off-by, since that would not apply to my own additions
Probably the only controversial thing is the item Pavel points
out about object_child_foreach iterators now being forbidden
from modifying the object composition tree.
Daniel P. Berrange (4):
qom: introduce object_property_foreach method
qmp: convert to use object_property_foreach iterators
vl: convert machine help to use object_property_foreach
qom: allow properties to be registered against classes
Pavel Fedin (1):
qom: replace object property list with GHashTable
include/qom/object.h | 78 ++++++++++++-
qmp.c | 103 +++++++++-------
qom/object.c | 325 +++++++++++++++++++++++++++++++++++++++++++++------
vl.c | 37 +++---
4 files changed, 444 insertions(+), 99 deletions(-)
--
2.4.3
next reply other threads:[~2015-10-08 14:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-08 14:08 Daniel P. Berrange [this message]
2015-10-08 14:09 ` [Qemu-devel] [PATCH v3 1/5] qom: introduce object_property_foreach method Daniel P. Berrange
2015-10-08 16:29 ` Eric Blake
2015-10-09 8:31 ` [Qemu-devel] Stick to loops (was: [PATCH v3 1/5] qom: introduce object_property_foreach method) Markus Armbruster
2015-10-12 10:00 ` Daniel P. Berrange
2015-10-12 10:24 ` [Qemu-devel] Stick to loops Paolo Bonzini
2015-10-12 11:56 ` Markus Armbruster
2015-10-13 12:09 ` [Qemu-devel] Stick to loops (was: [PATCH v3 1/5] qom: introduce object_property_foreach method) Daniel P. Berrange
2015-10-08 14:09 ` [Qemu-devel] [PATCH v3 2/5] qmp: convert to use object_property_foreach iterators Daniel P. Berrange
2015-10-08 16:35 ` Eric Blake
2015-10-08 14:09 ` [Qemu-devel] [PATCH v3 3/5] vl: convert machine help to use object_property_foreach Daniel P. Berrange
2015-10-08 19:06 ` Eric Blake
2015-10-08 14:09 ` [Qemu-devel] [PATCH v3 4/5] qom: replace object property list with GHashTable Daniel P. Berrange
2015-10-08 15:05 ` Pavel Fedin
2015-10-08 19:13 ` Eric Blake
2015-10-08 14:09 ` [Qemu-devel] [PATCH v3 5/5] qom: allow properties to be registered against classes Daniel P. Berrange
2015-10-08 19:35 ` Eric Blake
2015-10-08 15:12 ` [Qemu-devel] [PATCH v3 0/5] qom: more efficient object property handling Eric Blake
2015-10-08 15:27 ` Pavel Fedin
2015-10-08 15:48 ` Daniel P. Berrange
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=1444313344-16196-1-git-send-email-berrange@redhat.com \
--to=berrange@redhat.com \
--cc=afaerber@suse.de \
--cc=p.fedin@samsung.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 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).