From: "Denis V. Lunev" <den@openvz.org>
To: qemu-devel@nongnu.org
Cc: den@openvz.org, "Michael S. Tsirkin" <mst@redhat.com>,
Eric Blake <eblake@redhat.com>
Subject: [Qemu-devel] [RFC for 2.7 0/2] virtio: show guest features in 'info qtree'
Date: Wed, 11 May 2016 12:52:02 +0300 [thread overview]
Message-ID: <1462960324-4655-1-git-send-email-den@openvz.org> (raw)
It is very convinient and useful for debug purpose to expose the set of
features negotiated with guest. The patch exports those features via
read-only bit properties.
This patchset is a proof-of-concept on a base of virtio network device.
Signed-off-by: Denis V. Lunev <den@openvz.org>
CC: Michael S. Tsirkin <mst@redhat.com>
CC: Eric Blake <eblake@redhat.com>
Denis V. Lunev (2):
qdev: add read-only bit/bit64 property
virtio: show features acked by guest in 'info qtree' dump
hw/core/qdev-properties.c | 29 +++++++++++++++++++++++++++--
hw/net/virtio-net.c | 44 ++++++++++++++++++++++++++++++++++++++++++++
include/hw/qdev-properties.h | 18 ++++++++++++++++++
3 files changed, 89 insertions(+), 2 deletions(-)
--
2.5.0
next reply other threads:[~2016-05-11 9:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 9:52 Denis V. Lunev [this message]
2016-05-11 9:52 ` [Qemu-devel] [RFC 1/2] qdev: add read-only bit/bit64 property Denis V. Lunev
2016-05-11 9:52 ` [Qemu-devel] [RFC 2/2] virtio: show features acked by guest in 'info qtree' dump Denis V. Lunev
2016-05-11 17:24 ` Michael S. Tsirkin
2016-05-11 10:34 ` [Qemu-devel] [RFC for 2.7 0/2] virtio: show guest features in 'info qtree' Cornelia Huck
2016-05-11 11:06 ` Denis V. Lunev
2016-05-11 12:02 ` Cornelia Huck
2016-05-11 13:49 ` Denis V. Lunev
2016-05-11 14:27 ` Cornelia Huck
2016-05-11 10:39 ` Denis V. Lunev
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=1462960324-4655-1-git-send-email-den@openvz.org \
--to=den@openvz.org \
--cc=eblake@redhat.com \
--cc=mst@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).