From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Milian Wolff <milian.wolff@kdab.com>
Cc: David Ahern <dsahern@gmail.com>, linux-perf-users@vger.kernel.org
Subject: Re: [DONE] Re: Reordering the thread output in perf trace --summary
Date: Mon, 9 May 2016 17:12:55 -0300 [thread overview]
Message-ID: <20160509201255.GD13209@kernel.org> (raw)
In-Reply-To: <3442884.78Cb9YQhj3@milian-kdab2>
Em Mon, May 09, 2016 at 08:03:30PM +0200, Milian Wolff escreveu:
> On Monday, May 9, 2016 1:25:16 PM CEST Arnaldo Carvalho de Melo wrote:
> > I'll probably make it use the sched:sched_stat_runtime data as the sort
> > key for threads if --stat is used, what do you think?
> You mean if `--sched` was used? I'm undecided on this. On one hand, the user
> explicitly requests `--sched` so he probably is interested in it. On the other
> hand, the total number of syscalls or wait time per thread may be more
> interesting... If you use this to find contention issues e.g. then the threads
> suffering most from contention issues will have a low runtime.
> Personally, I think this is yet another situation where a proper GUI could
> solve this problem nicely. A trivial tree view with the option to adapt the
> sorting and aggregation as needed and a way to filter out certain syscalls
> post-collection would be really nice to have. I'm very much looking forward to
> having more time at hands again to finally tackle this.
Yeah, we could make that dynamic, the trace case is basically 'perf
top/report' working on two events at a a time (enter/exit).
In the end I think the best way would be to get 'perf trace' to use the
hists browser like top and report :-)
I.e. we would be showing that 'perf trace --summary' in "real time", to
abuse that term a bit more :-)
We would be producing it and refreshing it over time.
A generic mechanism for matching up pairs (or more) events and present
them together with things like callchains, like we do now specifically
for sys_enter/sys_exit syscall tracepoints would be handy indeed.
But feel encouraged to try a GUI to exercise your ideas, hopefully the
existing infrastructure can get readily used for that, let us know about
any change that you think would help with that.
- Arnaldo
prev parent reply other threads:[~2016-05-09 20:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-04 9:02 Reordering the thread output in perf trace --summary Milian Wolff
2016-05-04 9:51 ` Milian Wolff
2016-05-04 21:41 ` Arnaldo Carvalho de Melo
2016-05-05 16:04 ` [DONE] " Arnaldo Carvalho de Melo
2016-05-09 8:28 ` Milian Wolff
2016-05-09 16:25 ` Arnaldo Carvalho de Melo
2016-05-09 18:03 ` Milian Wolff
2016-05-09 20:12 ` Arnaldo Carvalho de Melo [this message]
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=20160509201255.GD13209@kernel.org \
--to=acme@kernel.org \
--cc=dsahern@gmail.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=milian.wolff@kdab.com \
/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).