From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Anton Kuchin <antonkuchin@yandex-team.ru>,
qemu-block@nongnu.org, libvir-list@redhat.com,
qemu-devel@nongnu.org, nsoffer@redhat.com,
Max Reitz <mreitz@redhat.com>,
Evgeny Yakovlev <wrfsh@yandex-team.ru>
Subject: Re: [Qemu-devel] [libvirt] [PATCH] qmp: Deprecate query-nodes option of query-blockstats
Date: Mon, 28 Jan 2019 16:12:57 +0000 [thread overview]
Message-ID: <20190128161257.GC3437@redhat.com> (raw)
In-Reply-To: <20190128153750.GE5756@localhost.localdomain>
On Mon, Jan 28, 2019 at 04:37:50PM +0100, Kevin Wolf wrote:
> Am 28.01.2019 um 16:15 hat Anton Kuchin geschrieben:
> > This option is broken since a6baa60807 in v2.9 and returns mostly
> > zeroes instead of real stats because actual querring of BlockStats
> > that resides in blk is missing.
> >
> > And it makes no sense because with this option BlockDriverState-s
> > are iterated but BlockAcctStats belong to BlockBackend and not BDS
> > since 7f0e9da6f13 in v2.5
> >
> > Signed-off-by: Anton Kuchin <antonkuchin@yandex-team.ru>
>
> Isn't query-nodes the only way to get wr_highest_offset for the protocol
> layer? oVirt depends on this, as far as I know.
Libvirt just invokes 'query-blockstats' with no arguments, so is not
relying on 'query-nodes' working. Given that libvirt doesn't use it,
it doesn't seem like this is relevant for oVirt unless they were
using QMP passthrough from libvirt. That this has been broken
since v2.9 though rather suggests oVirt doesn't use it.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2019-01-28 16:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 15:15 [Qemu-devel] [PATCH] qmp: Deprecate query-nodes option of query-blockstats Anton Kuchin
2019-01-28 15:37 ` Kevin Wolf
2019-01-28 16:12 ` Daniel P. Berrangé [this message]
2019-01-28 16:26 ` [Qemu-devel] [libvirt] " Kevin Wolf
2019-01-28 18:02 ` Nir Soffer
2019-01-28 17:33 ` [Qemu-devel] " Anton Kuchin
2019-01-28 16:04 ` Thomas Huth
2019-01-28 16:18 ` [Qemu-devel] [libvirt] " Daniel P. Berrangé
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=20190128161257.GC3437@redhat.com \
--to=berrange@redhat.com \
--cc=antonkuchin@yandex-team.ru \
--cc=kwolf@redhat.com \
--cc=libvir-list@redhat.com \
--cc=mreitz@redhat.com \
--cc=nsoffer@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=wrfsh@yandex-team.ru \
/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).