From: Steven Rostedt <rostedt@goodmis.org>
To: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
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: Thu, 10 Jun 2010 14:41:11 -0400 [thread overview]
Message-ID: <1276195271.28329.2.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <1276024211.15884.107.camel@gandalf.stny.rr.com>
On Tue, 2010-06-08 at 15:10 -0400, Steven Rostedt wrote:
> On Tue, 2010-06-08 at 23:05 +0530, Srikar Dronamraju wrote:
> > > On Tue, 2010-06-08 at 11:33 -0400, Steven Rostedt wrote:
>
> > I tested the patch and it fixed the regression where
> > perf record -e probe:do_fork -aR sleep 1 would fail.
> >
>
> Thanks! Unfortunately the patch does two things, one is to fix this
> regression, the other is a clean up. Linus is currently only wanting
> fixes now and may not accept the clean up part of this patch. Can you
> test the patch below. It only addresses the regression.
>
Peter,
Can I get an Acked-by from you on this patch? I know you acked the clean
up version. But this is a minimal fix for .35. We'll add the clean up
version to .36.
Thanks,
-- Steve
> diff --git a/kernel/trace/trace_event_perf.c b/kernel/trace/trace_event_perf.c
> index e6f6588..8a2b73f 100644
> --- a/kernel/trace/trace_event_perf.c
> +++ b/kernel/trace/trace_event_perf.c
> @@ -96,7 +96,9 @@ int perf_trace_init(struct perf_event *p_event)
> mutex_lock(&event_mutex);
> list_for_each_entry(tp_event, &ftrace_events, list) {
> if (tp_event->event.type == event_id &&
> - tp_event->class && tp_event->class->perf_probe &&
> + tp_event->class &&
> + (tp_event->class->perf_probe ||
> + tp_event->class->reg) &&
> try_module_get(tp_event->mod)) {
> ret = perf_trace_event_init(tp_event, p_event);
> break;
>
next prev parent reply other threads:[~2010-06-10 18:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-08 15:33 Steven Rostedt
2010-06-08 15:57 ` Peter Zijlstra
2010-06-08 17:35 ` Srikar Dronamraju
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 [this message]
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=1276195271.28329.2.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--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=srikar@linux.vnet.ibm.com \
/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
all inboxes | Powered by JetHome®