From: Frederic Weisbecker <fweisbec@gmail.com>
To: Jason Baron <jbaron@redhat.com>
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org, paulus@samba.org,
a.p.zijlstra@chello.nl, rostedt@goodmis.org
Subject: Re: [PATCH 0/2] perf_counter: add tracepoint support
Date: Thu, 9 Jul 2009 05:10:33 +0200 [thread overview]
Message-ID: <20090709031032.GA6412@nowhere> (raw)
In-Reply-To: <cover.1246912068.git.jbaron@redhat.com>
On Mon, Jul 06, 2009 at 05:11:53PM -0400, Jason Baron wrote:
>
> hi,
>
> The following two patches build on Peter's initial tracepoint perf counter work.
> The first patches enables the kernel side, and the second patch adds support to
> the 'perf' tool itself. The debugfs filesystem needs to be mounted to make this
> work and it is searched in the default location '/sys/kernel/debug'. We can
> add an optional parameter to search for it elsewhere if need be.
>
> Below, I show the output of 'perf list', and 'perf stat' for a tbench run.
>
[...]
> > perf stat -a -e sched:sched_switch -e sched:sched_wakeup -e irq:irq_handler_entry tbench 4
>
> Performance counter stats for 'tbench 4':
>
> 194658693 sched:sched_switch
> 97479295 sched:sched_wakeup
> 9122 irq:irq_handler_entry
>
> 720.171439729 seconds time elapsed
>
Cool, now the next stage that would be nice would be to have the
events themselves and not only the counts so that we can sort the
stats using values from the fields.
I have some ideas about that. We shouldn't interfere with ftrace job
and then use a private buffer for ftrace events used by perf.
But still this private buffer should be a private instance of the
ring buffer implemented in kernel/trace/, which is already well adapted for
the ftrace events (handles recursion).
(RFD parenthesis: why not using the one in kernel/trace for all perf events?
Now that it is lockless, it would fit nicely inside: no fear about NMI
context).
Anyway, unless you are already working on it, I'll try to adapt the content
of these events with perfcounter.
Thanks,
Frederic.
>
> -add kernel tracepoint support
> -add support for tracepoints to the perf tool
>
> init/Kconfig | 2 +-
> kernel/perf_counter.c | 6 +-
> tools/perf/util/parse-events.c | 195 +++++++++++++++++++++++++++++++++++++++-
> tools/perf/util/util.h | 2 +
> 4 files changed, 200 insertions(+), 5 deletions(-)
>
next prev parent reply other threads:[~2009-07-09 3:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-06 21:11 [PATCH 0/2] perf_counter: add tracepoint support Jason Baron
2009-07-06 21:11 ` [PATCH 1/2] perf_counter: cleanup kernel perf counter support for tracepoints Jason Baron
2009-07-06 21:12 ` [PATCH 2/2] perf_counter: add support to the 'perf' tool " Jason Baron
2009-07-07 8:29 ` Peter Zijlstra
2009-07-08 20:17 ` [PATCH 3/2] perf_counters: add debugfs dir option Jason Baron
2009-07-09 0:47 ` Frederic Weisbecker
2009-07-09 14:45 ` Jason Baron
2009-07-10 4:17 ` Ingo Molnar
2009-07-13 7:15 ` [PATCH 2/2] perf_counter: add support to the 'perf' tool for tracepoints Ingo Molnar
2009-07-09 3:10 ` Frederic Weisbecker [this message]
2009-07-09 7:58 ` [PATCH 0/2] perf_counter: add tracepoint support Peter Zijlstra
2009-07-10 3:53 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2009-07-21 16:20 Jason Baron
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=20090709031032.GA6412@nowhere \
--to=fweisbec@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=rostedt@goodmis.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