From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: qemu-devel@nongnu.org, qemu-block@nongnu.org, eblake@redhat.com,
mreitz@redhat.com, kwolf@redhat.com, armbru@redhat.com,
vsementsov@virtuozzo.com, den@openvz.org,
nshirokovskiy@virtuozzo.com
Cc: pizhenwei@bytedance.com
Subject: [Qemu-devel] [PATCH v3 0/2] improve block-latency-histogram-set
Date: Fri, 21 Dec 2018 19:53:39 +0300 [thread overview]
Message-ID: <20181221165341.23736-1-vsementsov@virtuozzo.com> (raw)
Support QOM path for block-latency-histogram-set and drop x- prefix.
Libvirt discussion (not yet updated for using id instead of device):
https://www.redhat.com/archives/libvir-list/2018-September/msg00011.html
v3: rebase on master, s/3.1/4.0.
v2: id,device -> id (with fall back to device name)
fix versions and all remaining x_ prefixes
Vladimir Sementsov-Ogievskiy (2):
qapi: move to QOM path for x-block-latency-histogram-set
qapi: drop x- from x-block-latency-histogram-set
qapi/block-core.json | 24 ++++++++++++------------
block/qapi.c | 12 ++++++------
blockdev.c | 24 ++++++++++++++++--------
3 files changed, 34 insertions(+), 26 deletions(-)
--
2.18.0
next reply other threads:[~2018-12-21 16:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-21 16:53 Vladimir Sementsov-Ogievskiy [this message]
2018-12-21 16:53 ` [Qemu-devel] [PATCH v3 1/2] qapi: move to QOM path for x-block-latency-histogram-set Vladimir Sementsov-Ogievskiy
2019-01-08 13:20 ` Markus Armbruster
2019-02-11 17:39 ` Vladimir Sementsov-Ogievskiy
2019-02-11 17:52 ` Kevin Wolf
2019-02-11 18:33 ` Vladimir Sementsov-Ogievskiy
2019-02-11 17:54 ` Kevin Wolf
2019-02-11 18:30 ` Vladimir Sementsov-Ogievskiy
2019-02-12 9:07 ` Kevin Wolf
2019-02-12 9:51 ` Vladimir Sementsov-Ogievskiy
2018-12-21 16:53 ` [Qemu-devel] [PATCH v3 2/2] qapi: drop x- from x-block-latency-histogram-set Vladimir Sementsov-Ogievskiy
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=20181221165341.23736-1-vsementsov@virtuozzo.com \
--to=vsementsov@virtuozzo.com \
--cc=armbru@redhat.com \
--cc=den@openvz.org \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=nshirokovskiy@virtuozzo.com \
--cc=pizhenwei@bytedance.com \
--cc=qemu-block@nongnu.org \
--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).