From: Igor Mammedov <imammedo@redhat.com>
To: qemu-devel@nongnu.org
Cc: stefanha@redhat.com, sw@weilnetz.de, mjt@tls.msk.ru,
lcapitulino@redhat.com, blauwirbel@gmail.com,
aliguori@amazon.com, pbonzini@redhat.com, afaerber@suse.de,
rth@twiddle.net
Subject: [Qemu-devel] [RFC 0/5] -object/object-add support custom location and 2nd stage initialization
Date: Wed, 8 Jan 2014 17:09:37 +0100 [thread overview]
Message-ID: <1389197382-25085-1-git-send-email-imammedo@redhat.com> (raw)
Adds optional interfaces that objects could implement if
they need to:
1. perform an additional initialization after object properties are set
2. be placed not in '/objects' container
Series depends on 2 PULL requests in flight from Andreas & Luiz
with fixes for QOM interfaces and object-add monitor/QMP command.
Git tree for testing:
https://github.com/imammedo/qemu/commits/extend-object-add
Igor Mammedov (5):
object_add: consolidate error handling
add optional 2nd stage initialization to
-object/object-add/object_add commands
virtio_rng: use object_realize interface instead of calling backend
API
vl.c: -object: handle duplicate 'id' properly
-object/object-add: use custom default object location if provided
backends/rng.c | 17 ++++++-
hw/virtio/virtio-rng.c | 15 ++++---
include/qom/object_interfaces.h | 96 +++++++++++++++++++++++++++++++++++++++
include/sysemu/rng.h | 11 -----
qmp.c | 30 +++++++++---
qom/Makefile.objs | 1 +
qom/object_interfaces.c | 57 +++++++++++++++++++++++
vl.c | 21 ++++++++-
8 files changed, 220 insertions(+), 28 deletions(-)
create mode 100644 include/qom/object_interfaces.h
create mode 100644 qom/object_interfaces.c
next reply other threads:[~2014-01-08 16:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 16:09 Igor Mammedov [this message]
2014-01-08 16:09 ` [Qemu-devel] [PATCH 1/5] object_add: consolidate error handling Igor Mammedov
2014-01-08 16:09 ` [Qemu-devel] [PATCH 2/5] add optional 2nd stage initialization to -object/object-add/object_add commands Igor Mammedov
2014-01-08 16:09 ` [Qemu-devel] [PATCH 3/5] virtio_rng: use object_realize interface instead of calling backend API Igor Mammedov
2014-01-08 16:09 ` [Qemu-devel] [PATCH 4/5] vl.c: -object: handle duplicate 'id' properly Igor Mammedov
2014-01-08 16:09 ` [Qemu-devel] [PATCH 5/5] -object/object-add: use custom default object location if provided Igor Mammedov
2014-01-09 4:35 ` Stefan Hajnoczi
2014-01-10 10:59 ` Igor Mammedov
2014-01-08 16:24 ` [Qemu-devel] [RFC 0/5] -object/object-add support custom location and 2nd stage initialization Paolo Bonzini
2014-01-08 16:45 ` Andreas Färber
2014-01-08 17:00 ` Igor Mammedov
2014-01-08 16:51 ` Igor Mammedov
2014-01-08 17:33 ` Paolo Bonzini
2014-01-10 11:28 ` Igor Mammedov
2014-01-10 11:38 ` Paolo Bonzini
2014-01-10 14:44 ` Igor Mammedov
2014-01-10 15:40 ` Paolo Bonzini
2014-01-10 15:31 ` Igor Mammedov
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=1389197382-25085-1-git-send-email-imammedo@redhat.com \
--to=imammedo@redhat.com \
--cc=afaerber@suse.de \
--cc=aliguori@amazon.com \
--cc=blauwirbel@gmail.com \
--cc=lcapitulino@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=stefanha@redhat.com \
--cc=sw@weilnetz.de \
/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).