From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>, Jiri Olsa <jolsa@redhat.com>,
Stephane Eranian <eranian@google.com>,
Namhyung Kim <namhyung.kim@lge.com>,
Pekka Enberg <penberg@kernel.org>
Subject: Re: [PATCH 08/13] perf gtk/browser: Add support for event group view
Date: Wed, 23 Jan 2013 14:59:49 -0300 [thread overview]
Message-ID: <20130123175949.GB6687@ghostprotocols.net> (raw)
In-Reply-To: <87pq0xkbcj.fsf@sejong.aot.lge.com>
Em Tue, Jan 22, 2013 at 02:58:36PM +0900, Namhyung Kim escreveu:
> Hi Arnaldo,
>
> On Wed, 16 Jan 2013 15:28:59 -0300, Arnaldo Carvalho de Melo wrote:
> > Em Wed, Jan 16, 2013 at 07:25:02PM +0900, Namhyung Kim escreveu:
> >> Adding current header name to event name will fix the problem but it
> >> probably occupies too much screen width especially for long named
> >> tracepoint or PMU-specific events like
> >> "compaction:mm_compaction_isolate_migratepages".
> >>
> >> Overhead/branches Overhead/branch-misses sys/branches sys/branch-misses usr/branches usr/branch-misses Command Shared Object Symbol
> >> ................. ...................... ............ ................. ............ ................. ....... ............. .......
> >> 98.32% 31.16% 0.00% 0.00% 98.32% 31.16% a.out a.out [.] foo
> >>
> >>
> >> If you have a better idea or other way to place the cursor without
> >> printing bogus 0.00% on GTK, please let me know.
> >
> > Compacting it using an extra line:
> >
> > Overhead............... sys.................... usr....................
> > branches branch-misses branches branch-misses branches branch-misses Command Shared Object Symbol
> > ........ ............. ........ ............. ........ ............. ....... ............. .......
> > 98.32% 31.16% 0.00% 0.00% 98.32% 31.16% a.out a.out [.] foo
> >
> > It could even use some reference:
> >
> > Overhead..................... sys......... usr...........
> > branches(1) branch-misses(2) (1) (2) (1) (2) Command Shared Object Symbol
> > ........... ................ ..... ..... ...... ...... ....... ............. .......
> > 98.32% 31.16% 0.00% 0.00% 98.32% 31.16% a.out a.out [.] foo
> >
> > The (1) could be done with a superscript number or even just using a
> > different fore/background color, to use fewer columns.
> >
> > One other way, that would scale for really long event names, would be to
> > have the event list in the first few lines and then:
> >
> > Events:
> > 1. branches
> > 2. branch-misses
> >
> > Overhead...... sys......... usr...........
> > (1) (2) (1) (2) (1) (2) Command Shared Object Symbol
> > ...... ...... ..... ..... ...... ...... ....... ............. .......
> > 98.32% 31.16% 0.00% 0.00% 98.32% 31.16% a.out a.out [.] foo
> >
> > I think you could switch to/from each of these forms using a hotkey,
> > that would influence how the hist_entry__snprintf() routine would work,
> > either using perf_evsel__name() or evsel->idx :-)
> >
> > This way if at some point the user wants to expand/compress the lines,
> > it will be possible to do so quickly, just pressing the hotkey.
>
> By saying hotkey, I guess you meant to use it for TUI. However TUI
> doesn't provide those header lines. ;-)
See? I was trying to hit two rabbits with one stone, but you realised
that...
> As this extra line (and hotkey) thing might add complexity to the
> patchset, I'd like to separate it to a different work and to focus on
> the basic feature with current behavior. Is it acceptable for you?
Sure thing.
- Arnaldo
next prev parent reply other threads:[~2013-01-23 17:59 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 7:31 [PATCHSET 00/13] perf report: Add support for event group view (v8) Namhyung Kim
2013-01-15 7:31 ` [PATCH 01/13] perf tools: Keep group information Namhyung Kim
2013-01-15 7:31 ` [PATCH 02/13] perf tests: Add group test conditions Namhyung Kim
2013-01-15 7:31 ` [PATCH 03/13] perf header: Add HEADER_GROUP_DESC feature Namhyung Kim
2013-01-15 7:31 ` [PATCH 04/13] perf report: Make another loop for linking group hists Namhyung Kim
2013-01-15 7:31 ` [PATCH 05/13] perf hists: Resort hist entries using group members for output Namhyung Kim
2013-01-15 18:29 ` Arnaldo Carvalho de Melo
2013-01-16 9:20 ` Namhyung Kim
2013-01-15 7:31 ` [PATCH 06/13] perf ui/hist: Add support for event group view Namhyung Kim
2013-01-15 18:31 ` Arnaldo Carvalho de Melo
2013-01-16 9:22 ` Namhyung Kim
2013-01-16 18:14 ` Arnaldo Carvalho de Melo
2013-01-15 7:31 ` [PATCH 07/13] perf hist browser: " Namhyung Kim
2013-01-15 18:32 ` Arnaldo Carvalho de Melo
2013-01-16 9:52 ` Namhyung Kim
2013-01-15 7:31 ` [PATCH 08/13] perf gtk/browser: " Namhyung Kim
2013-01-15 18:34 ` Arnaldo Carvalho de Melo
2013-01-16 10:25 ` Namhyung Kim
2013-01-16 18:28 ` Arnaldo Carvalho de Melo
2013-01-22 5:58 ` Namhyung Kim
2013-01-23 17:59 ` Arnaldo Carvalho de Melo [this message]
2013-01-15 7:31 ` [PATCH 09/13] perf gtk/browser: Trim column header string when event group enabled Namhyung Kim
2013-01-15 7:31 ` [PATCH 10/13] perf report: Bypass non-leader events when event group is enabled Namhyung Kim
2013-01-15 7:31 ` [PATCH 11/13] perf report: Show group description " Namhyung Kim
2013-01-15 7:31 ` [PATCH 12/13] perf report: Add --group option Namhyung Kim
2013-01-15 7:31 ` [PATCH 13/13] perf report: Add report.group config option Namhyung Kim
2013-01-15 18:38 ` [PATCHSET 00/13] perf report: Add support for event group view (v8) Arnaldo Carvalho de Melo
2013-01-16 10:33 ` Namhyung Kim
2013-01-16 18:29 ` Arnaldo Carvalho de Melo
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=20130123175949.GB6687@ghostprotocols.net \
--to=acme@ghostprotocols.net \
--cc=a.p.zijlstra@chello.nl \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung.kim@lge.com \
--cc=namhyung@kernel.org \
--cc=paulus@samba.org \
--cc=penberg@kernel.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