On Mon, Oct 22, 2012 at 05:51:01PM +0900, Namhyung Kim wrote:
> On Mon, 22 Oct 2012 10:09:31 +0200, Jiri Olsa wrote:
> > On Sun, Oct 21, 2012 at 06:38:49PM +0200, Ingo Molnar wrote:
> >> > #
> >> > # Samples: 86 of event 'anon group { cycles, cache-misses }'
> >> > # Event count (approx.): 34863674
> >> > #
> >> > # Overhead Period Command Shared
> >> > Object Symbol
> >> > # ................ ........................ .......
> >> > ................. ................................
> >>
> >> Might make sense to consider this column enumeration:
> >>
> >> #
> >> # cycles
> >> # | cache-misses
> >> # | |
> >> > # v v
> >> > #
> >> > 16.56% 19.47% 5773450 475 ls
> >> > [kernel.kallsyms] [k] native_sched_clock
> >> > 10.87% 0.74% 3789088 18 ls
> >> > [kernel.kallsyms] [k] rtl8169_interrupt
> >
> > no problem in '--stdio' mode I guess.. not sure in '--tui/--gtk', Namhyung?
>
> I thought a similar way but met a problem. We have other output columns
> than 'overhead' like 'period' in this example. What about others?
> Adding all event names for each column will just increase the column
> width so bothers user IMHO - especially for pmu format events.
how about each event name is in special row as outlined above
should be no problem in stdio and could be optional (key toggled) in tui
jirka
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
