From: Roman Kagan <rkagan@virtuozzo.com>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: "Amit Shah" <amit@kernel.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Fam Zheng" <fam@euphon.net>,
"Markus Armbruster" <armbru@redhat.com>,
"Andreas Färber" <afaerber@suse.de>
Subject: [Qemu-devel] [RFC PATCH 0/5] expose negotiated virtio features in r/o properties
Date: Fri, 14 Dec 2018 16:57:05 +0000 [thread overview]
Message-ID: <20181214165657.749-1-rkagan@virtuozzo.com> (raw)
This series is an attempt to make virtio features acknowledged by the
guest visible as read-only QOM properties. One potential usecase of
this is debugging; another is when the upper layer needs to do something
only when/if the guest has acknowledged the support for a feature (e.g.
hot-plug a VFIO device once the guest claims VIRTIO_NET_F_STANDBY
support).
Being an RFC, it's incomplete and fails checkpatch, but I'd be intersted
to know if the approach is sane and worthwhile before I invest more time
in it.
Roman Kagan (5):
qom: preserve get/set presence in aliased properties
qmp: further consolidate listing of device and object properties
qdev-properties: add r/o 64bit bitfield property
virtio: drop DEFINE_VIRTIO_COMMON_FEATURES
virtio: expose negotiated features in r/o properties
include/hw/qdev-properties.h | 9 ++++
include/hw/virtio/virtio-scsi.h | 2 +-
include/hw/virtio/virtio.h | 18 +++----
hw/char/virtio-serial-bus.c | 6 ++-
hw/core/qdev-properties.c | 9 +++-
hw/net/virtio-net.c | 88 +++++++++++++++++--------------
hw/scsi/virtio-scsi.c | 4 +-
hw/virtio/virtio.c | 11 +++-
qmp.c | 92 ++++++++-------------------------
qom/object.c | 4 +-
10 files changed, 113 insertions(+), 130 deletions(-)
--
2.19.2
next reply other threads:[~2018-12-14 16:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 16:57 Roman Kagan [this message]
2018-12-14 16:57 ` [Qemu-devel] [RFC PATCH 1/5] qom: preserve get/set presence in aliased properties Roman Kagan
2018-12-14 16:57 ` [Qemu-devel] [RFC PATCH 2/5] qmp: further consolidate listing of device and object properties Roman Kagan
2018-12-14 16:57 ` [Qemu-devel] [RFC PATCH 3/5] qdev-properties: add r/o 64bit bitfield property Roman Kagan
2018-12-14 16:57 ` [Qemu-devel] [RFC PATCH 4/5] virtio: drop DEFINE_VIRTIO_COMMON_FEATURES Roman Kagan
2018-12-14 16:57 ` [Qemu-devel] [RFC PATCH 5/5] virtio: expose negotiated features in r/o properties Roman Kagan
2018-12-23 11:05 ` [Qemu-devel] [RFC PATCH 0/5] expose negotiated virtio " no-reply
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=20181214165657.749-1-rkagan@virtuozzo.com \
--to=rkagan@virtuozzo.com \
--cc=afaerber@suse.de \
--cc=amit@kernel.org \
--cc=armbru@redhat.com \
--cc=fam@euphon.net \
--cc=mst@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).