From: Namhyung Kim <namhyung@kernel.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@elte.hu>, Paul Mackerras <paulus@samba.org>,
Corey Ashford <cjashfor@linux.vnet.ibm.com>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [PATCH 00/11] perf tool: Add PERF_SAMPLE_READ sample read support
Date: Mon, 22 Oct 2012 17:51:01 +0900 [thread overview]
Message-ID: <87a9vekhze.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <20121022080930.GB984@krava.brq.redhat.com> (Jiri Olsa's message of "Mon, 22 Oct 2012 10:09:31 +0200")
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.
So I ended up printing those events on the header:
# Samples: 86 of event 'anon group { cycles, cache-misses }'
Thanks,
Namhyung
next prev parent reply other threads:[~2012-10-22 8:51 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-20 14:33 [PATCH 00/11] perf tool: Add PERF_SAMPLE_READ sample read support Jiri Olsa
2012-10-20 14:33 ` [PATCH 01/11] perf: Add PERF_EVENT_IOC_ID ioctl to return event ID Jiri Olsa
2012-10-20 14:33 ` [PATCH 02/11] perf: Do not get values from disabled counters in group format read Jiri Olsa
2012-10-23 16:13 ` Peter Zijlstra
2012-10-23 16:50 ` Jiri Olsa
2012-10-24 12:01 ` Peter Zijlstra
2012-10-24 12:14 ` Jiri Olsa
2012-10-24 12:32 ` Peter Zijlstra
2012-10-24 16:03 ` Jiri Olsa
2012-10-20 14:33 ` [PATCH 03/11] perf tool: Use PERF_EVENT_IOC_ID perf ioctl to read event id Jiri Olsa
2012-10-22 7:57 ` Namhyung Kim
2012-10-22 8:40 ` Jiri Olsa
2012-10-20 14:33 ` [PATCH 04/11] perf tool: Add support for parsing PERF_SAMPLE_READ sample type Jiri Olsa
2012-10-22 8:56 ` Namhyung Kim
2012-10-20 14:33 ` [PATCH 05/11] perf tool: Fix event ID retrieval for group format read case Jiri Olsa
2012-10-20 14:33 ` [PATCH 06/11] perf tool: Add perf_evlist__id2sid function to get event ID related data Jiri Olsa
2012-10-20 14:33 ` [PATCH 07/11] perf tool: Add PERF_SAMPLE_READ sample related processing Jiri Olsa
2012-10-20 14:33 ` [PATCH 08/11] perf tool: Add 'S' event/group modifier to read sample value Jiri Olsa
2012-10-20 14:33 ` [PATCH 09/11] perf test: Add parse events tests for leader sampling Jiri Olsa
2012-10-22 8:58 ` Namhyung Kim
2012-10-22 9:12 ` Jiri Olsa
2012-10-20 14:33 ` [PATCH 10/11] perf tool: Display period values for all group members Jiri Olsa
2012-10-20 14:33 ` [PATCH 11/11] perf record: Fix mmap error output condition Jiri Olsa
2012-10-30 12:11 ` [tip:perf/core] " tip-bot for Jiri Olsa
2012-10-21 16:38 ` [PATCH 00/11] perf tool: Add PERF_SAMPLE_READ sample read support Ingo Molnar
2012-10-22 8:09 ` Jiri Olsa
2012-10-22 8:51 ` Namhyung Kim [this message]
2012-10-22 9:15 ` Jiri Olsa
2012-10-22 7:32 ` Namhyung Kim
2012-10-22 7:53 ` Jiri Olsa
2012-10-22 8:53 ` Namhyung Kim
2012-10-22 9:06 ` Jiri Olsa
2012-10-26 1:29 ` Namhyung Kim
2012-10-26 9:14 ` Peter Zijlstra
2012-10-26 10:23 ` Jiri Olsa
2012-10-26 15:39 ` Namhyung Kim
2012-10-26 16:14 ` David Ahern
2012-10-26 16:25 ` Namhyung Kim
2012-10-26 16:47 ` David Ahern
2012-10-26 17:00 ` Arnaldo Carvalho de Melo
2013-02-04 12:32 Jiri Olsa
2013-02-06 4:59 ` Namhyung Kim
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=87a9vekhze.fsf@sejong.aot.lge.com \
--to=namhyung@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=cjashfor@linux.vnet.ibm.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@kernel.org \
--cc=paulus@samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.