From: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
To: Peter Zijlstra <peterz@infradead.org>, rostedt@goodmis.org
Cc: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Frederic Weisbecker <fweisbec@gmail.com>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
Ananth N Mavinakayanahalli <ananth@in.ibm.com>
Subject: Re: [PATCH][RFC] tracing: Use class->reg() for all registering of events
Date: Tue, 8 Jun 2010 23:05:59 +0530 [thread overview]
Message-ID: <20100608173559.GE2800@linux.vnet.ibm.com> (raw)
In-Reply-To: <1276012661.2046.120.camel@twins>
> On Tue, 2010-06-08 at 11:33 -0400, Steven Rostedt wrote:
> > I'm pushing this as an RFC first. This probably should be something that
> > makes it into 2.6.35.
> >
> > Acks and perhaps a little testing from the perf and kprobe angle?
>
> I'll have a look soon, but lets add Srikar to CC, he actually reported
> the problem :-)
>
> > Steven Rostedt (1):
> > tracing: Use class->reg() for all registering of evints
> >
I tested the patch and it fixed the regression where
perf record -e probe:do_fork -aR sleep 1 would fail.
Now with this patch, it records the events. However perf record
encounters a floating point exception .. (Peter said he was aware and had a
fix for the floating point exception problem)
However I still see another minor regression (atleast on the tip tree)
This regression was present even before this patch.
The first time I run a perf probe command, it fails, subsequent runs
pass.
i.e
411 [srikar@llm69 ]$ sudo perf probe do_fork
kprobe_events file does not exist - please rebuild kernel with CONFIG_KPROBE_EVENT.
Error: Failed to add events. (-1)
411 [srikar@llm69 ]$ sudo perf probe do_fork
Add new event:
probe:do_fork (on do_fork)
You can now use it on all perf tools, such as:
perf record -e probe:do_fork -aR sleep 1
411 [srikar@llm69 ]$
--
Thanks and Regards
Srikar
next prev parent reply other threads:[~2010-06-08 17:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-08 15:33 [PATCH][RFC] tracing: Use class->reg() for all registering of events Steven Rostedt
2010-06-08 15:57 ` Peter Zijlstra
2010-06-08 17:35 ` Srikar Dronamraju [this message]
2010-06-08 19:10 ` Steven Rostedt
2010-06-08 19:11 ` Steven Rostedt
2010-06-09 5:05 ` Srikar Dronamraju
2010-06-09 6:32 ` Peter Zijlstra
2010-06-09 11:47 ` Srikar Dronamraju
2010-06-09 11:53 ` Peter Zijlstra
2010-06-09 12:02 ` Arnaldo Carvalho de Melo
2010-06-09 12:23 ` Arnaldo Carvalho de Melo
2010-06-09 12:35 ` Arnaldo Carvalho de Melo
2010-06-10 8:27 ` Srikar Dronamraju
2010-06-10 14:07 ` Arnaldo Carvalho de Melo
2010-06-10 14:52 ` Steven Rostedt
2010-06-10 15:12 ` Srikar Dronamraju
2010-06-10 18:41 ` Steven Rostedt
2010-06-10 20:36 ` Peter Zijlstra
2010-06-10 20:41 ` Steven Rostedt
2010-06-08 18:36 ` Peter Zijlstra
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=20100608173559.GE2800@linux.vnet.ibm.com \
--to=srikar@linux.vnet.ibm.com \
--cc=ananth@in.ibm.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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 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.