From: "Emilio G. Cota" <cota@braap.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org,
Peter Crosthwaite <crosthwaite.peter@gmail.com>,
Richard Henderson <rth@twiddle.net>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Stefan Weil <sw@weilnetz.de>,
Markus Armbruster <armbru@redhat.com>,
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:26:09 -0400 [thread overview]
Message-ID: <20180815012609.GC17669@flamenco> (raw)
In-Reply-To: <2f2b1597-6cb1-b6ae-b2a0-38c54e1c34d1@redhat.com>
On Tue, Aug 14, 2018 at 10:14:01 +0200, Paolo Bonzini wrote:
> On 13/08/2018 19:11, Emilio G. Cota wrote:
> Would it make sense to add a flag to sort by average wait time
Done:
(qemu) help info sync-profile
info sync-profile [-m] [max] -- show sync profiling info \
for up to max entries (default: 10). By default, entries \
are sorted by total wait time; -m sorts by mean wait time.
(qemu) info sync-profile 3
Type Object Call site Wait Time (s) Count Average (us)
------------------------------------------------------------------------------------
condvar 0x560cc9909e50 cpus.c:1165 63.63428 16081 3957.11
condvar 0x560cc9909e50 cpus.c:1415 0.21074 2 105371.07
BQL mutex 0x560cc85a3fa0 util/rcu.c:269 0.20227 20 10113.60
------------------------------------------------------------------------------------
(qemu) info sync-profile -m 3
Type Object Call site Wait Time (s) Count Average (us)
------------------------------------------------------------------------------------
condvar 0x560cc9909e50 cpus.c:1415 0.21074 2 105371.07
BQL mutex 0x560cc85a3fa0 util/rcu.c:269 0.20227 21 9632.00
condvar 0x560cc9909e50 cpus.c:1165 71.92799 18167 3959.27
------------------------------------------------------------------------------------
>, and one to coalesce all mutexes for the same call site?
I am not sure I understand. Do you mean to pass a specific call site,
so that we coalesce all entries related to the call site's object?
Or to keep the call sites separate, but only report entries related
to that specific call site's object?
Thanks,
Emilio
next prev parent reply other threads:[~2018-08-15 1:26 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 [this message]
2018-08-16 13:20 ` Peter Xu
2018-08-14 9:43 ` Dr. David Alan Gilbert
2018-08-15 1:33 ` Emilio G. Cota
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=20180815012609.GC17669@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).