From: "Emilio G. Cota" <cota@braap.org>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
Peter Crosthwaite <crosthwaite.peter@gmail.com>,
Richard Henderson <rth@twiddle.net>, Stefan Weil <sw@weilnetz.de>,
Peter Xu <peterx@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 2/3] monitor: show sync profiling info with 'info sync'
Date: Tue, 14 Aug 2018 21:33:47 -0400 [thread overview]
Message-ID: <20180815013347.GD17669@flamenco> (raw)
In-Reply-To: <87o9e5rl4b.fsf@dusky.pond.sub.org> <20180814094347.GE2580@work-vm>
On Tue, Aug 14, 2018 at 10:43:47 +0100, Dr. David Alan Gilbert wrote:
> * Emilio G. Cota (cota@braap.org) wrote:
> > +@item info sync
>
> As long as this is just for devs I'm OK with this from the HMP side;
> however, if you want to automate the display or wire it to other
> tools then you should probably wire it up via QMP.
On Tue, Aug 14, 2018 at 18:03:32 +0200, Markus Armbruster wrote:
> "Emilio G. Cota" <cota@braap.org> writes:
> > +@item info sync
>
> Please explain briefly why you think this command is not going to be
> useful in QMP. Recommend to do that right in your commit message. For
> instance, you could argue that the information provided is useful only
> to developers, and developers are just fine with getting it from HMP
> "info sync".
>
> However, if we expect developers to further process the data, providing
> it as JSON (via QMP) makes sense, because is saves them the trouble of
> parsing your (undocumented) HMP output format.
>
> If we decide we want to provide the functionality in QMP, I can help you
> with the necessary code changes.
Thanks Dave and Markus for taking a look.
This is just for developers. This means (1) the info displayed and the
output format could change in the future, and (2) it is only meant
to be used from HMP "info sync-profile".
I'll include the above in the commit log, as Markus suggested.
> > + .name = "sync",
>
> I think "info sync-profile" would be clearer.
Done.
Thanks,
Emilio
next prev parent reply other threads:[~2018-08-15 1:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-13 17:11 [Qemu-devel] [PATCH 0/3] synchronization profiler Emilio G. Cota
2018-08-13 17:11 ` [Qemu-devel] [PATCH 1/3] qsp: QEMU's Synchronization Profiler Emilio G. Cota
2018-08-14 8:13 ` Paolo Bonzini
2018-08-15 0:44 ` Emilio G. Cota
2018-08-15 4:29 ` Markus Armbruster
2018-08-15 3:09 ` Fam Zheng
2018-08-15 4:53 ` Emilio G. Cota
2018-08-15 7:04 ` Fam Zheng
2018-08-15 23:55 ` Emilio G. Cota
2018-08-16 4:29 ` Emilio G. Cota
2018-08-16 4:36 ` Fam Zheng
2018-08-13 17:11 ` [Qemu-devel] [PATCH 2/3] monitor: show sync profiling info with 'info sync' Emilio G. Cota
2018-08-14 8:14 ` Paolo Bonzini
2018-08-15 1:26 ` Emilio G. Cota
2018-08-16 13:20 ` Peter Xu
2018-08-14 9:43 ` Dr. David Alan Gilbert
2018-08-15 1:33 ` Emilio G. Cota [this message]
2018-08-14 16:03 ` Markus Armbruster
2018-08-13 17:11 ` [Qemu-devel] [PATCH 3/3] qsp: track BQL callers directly Emilio G. Cota
2018-08-15 23:30 ` [Qemu-devel] [PATCH 0/3] synchronization profiler 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=20180815013347.GD17669@flamenco \
--to=cota@braap.org \
--cc=armbru@redhat.com \
--cc=crosthwaite.peter@gmail.com \
--cc=dgilbert@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=sw@weilnetz.de \
/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).