From: Fam Zheng <famz@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Dr . David Alan Gilbert" <dgilbert@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Andreas Färber" <afaerber@suse.de>,
"Markus Armbruster" <armbru@redhat.com>
Subject: [Qemu-devel] [PATCH v2 0/7] qdev: Introduce DEFINE_PROP_LINK
Date: Thu, 29 Jun 2017 16:04:45 +0800 [thread overview]
Message-ID: <20170629080452.26470-1-famz@redhat.com> (raw)
v2: Create a new header for link properties. [Paolo]
Don't wrap, use PropertyInfo.create() (much better diffstat, yay!).
[Paolo]
Link properties of devices created with object_property_add_link() are not
reflected in HMP "info qtree". For example, whether a virtio-blk device has an
iothread (i.e. has enabled data plane) can not be introspected easily.
Introduce a new type of qdev property macro to fix that.
Fam Zheng (7):
qom: Make link property API public
qom: Handle property lookup failure in object_resolve_link
qdev: Introduce PropertyInfo.create
qdev: Introduce DEFINE_PROP_LINK
virtio-blk: Use DEFINE_PROP_LINK
virtio-scsi: Use DEFINE_PROP_LINK
virtio-rng: Use DEFINE_PROP_LINK
hw/block/dataplane/virtio-blk.c | 2 +-
hw/block/virtio-blk.c | 7 +++----
hw/core/qdev-properties.c | 16 ++++++++++++++++
hw/core/qdev.c | 31 +++++++++++++++++++------------
hw/scsi/virtio-scsi-dataplane.c | 2 +-
hw/scsi/virtio-scsi.c | 15 ++++-----------
hw/virtio/virtio-pci.c | 6 ------
hw/virtio/virtio-rng.c | 16 ++++------------
include/hw/qdev-core.h | 6 ++++++
include/hw/qdev-properties.h | 11 +++++++++++
include/hw/virtio/virtio-blk.h | 2 +-
include/hw/virtio/virtio-rng.h | 2 +-
include/hw/virtio/virtio-scsi.h | 2 +-
include/qom/link-property.h | 31 +++++++++++++++++++++++++++++++
qom/object.c | 24 +++++++++++-------------
15 files changed, 110 insertions(+), 63 deletions(-)
create mode 100644 include/qom/link-property.h
--
2.9.4
next reply other threads:[~2017-06-29 8:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-29 8:04 Fam Zheng [this message]
2017-06-29 8:04 ` [Qemu-devel] [PATCH v2 1/7] qom: Make link property API public Fam Zheng
2017-06-29 8:04 ` [Qemu-devel] [PATCH v2 2/7] qom: Handle property lookup failure in object_resolve_link Fam Zheng
2017-06-29 8:04 ` [Qemu-devel] [PATCH v2 3/7] qdev: Introduce PropertyInfo.create Fam Zheng
2017-06-29 8:04 ` [Qemu-devel] [PATCH v2 4/7] qdev: Introduce DEFINE_PROP_LINK Fam Zheng
2017-06-29 10:40 ` Igor Mammedov
2017-06-29 11:11 ` Fam Zheng
2017-06-29 11:51 ` Paolo Bonzini
2017-06-29 11:58 ` Fam Zheng
2017-06-29 8:04 ` [Qemu-devel] [PATCH v2 5/7] virtio-blk: Use DEFINE_PROP_LINK Fam Zheng
2017-06-29 8:04 ` [Qemu-devel] [PATCH v2 6/7] virtio-scsi: " Fam Zheng
2017-06-29 8:04 ` [Qemu-devel] [PATCH v2 7/7] virtio-rng: " Fam Zheng
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=20170629080452.26470-1-famz@redhat.com \
--to=famz@redhat.com \
--cc=afaerber@suse.de \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=pbonzini@redhat.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).