From: Wu Fengguang <fengguang.wu@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Steven Rostedt <srostedt@redhat.com>
Subject: Re: perf regression: failed to stat syscalls events
Date: Thu, 24 Jun 2010 14:38:29 +0800 [thread overview]
Message-ID: <20100624063829.GA6501@localhost> (raw)
In-Reply-To: <1277359125.1875.828.camel@laptop>
On Thu, Jun 24, 2010 at 01:58:45PM +0800, Peter Zijlstra wrote:
> On Thu, 2010-06-24 at 09:44 +0800, Wu Fengguang wrote:
> > On Thu, Jun 24, 2010 at 09:39:15AM +0800, Wu Fengguang wrote:
> > > Greetings,
> > >
> > > I noticed that
> > >
> > > # perf stat -e syscalls:sys_enter_mmap true
> > >
> > > refuse to work on 2.6.35-rc1. The last working kernel is 2.6.34.
> >
> > Other events like lock:* or block:* or whatever continue to work.
> > So this is a problem specific to syscalls:*.
>
> Does your tree contain:
Thanks, it worked! This patch is missing from linux-2.6.git for now.
Thanks,
Fengguang
> ---
> commit a8fb2608053547bc3152ea61a5ec7cdfce5d942c
> Author: Steven Rostedt <srostedt@redhat.com>
> Date: Thu Jun 10 14:53:16 2010 -0400
>
> perf/tracing: Fix regression of perf losing kprobe events
>
> With the addition of the code to shrink the kernel tracepoint
> infrastructure, we lost kprobes being traced by perf. The reason
> is that I tested if the "tp_event->class->perf_probe" existed before
> enabling it. This prevents "ftrace only" events (like the function
> trace events) from being enabled by perf.
>
> Unfortunately, kprobe events do not use perf_probe. This causes
> kprobes to be missed by perf. To fix this, we add the test to
> see if "tp_event->class->reg" exists as well as perf_probe.
>
> Normal trace events have only "perf_probe" but no "reg" function,
> and kprobes and syscalls have the "reg" but no "perf_probe".
> The ftrace unique events do not have either, so this is a valid
> test. If a kprobe or syscall is not to be probed by perf, the
> "reg" function is called anyway, and will return a failure and
> prevent perf from probing it.
>
> Reported-by: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
> Tested-by: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
> Acked-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
> Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
>
> 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;
>
prev parent reply other threads:[~2010-06-24 6:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-24 1:39 perf regression: failed to stat syscalls events Wu Fengguang
2010-06-24 1:44 ` Wu Fengguang
2010-06-24 5:58 ` Peter Zijlstra
2010-06-24 6:38 ` Wu Fengguang [this message]
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=20100624063829.GA6501@localhost \
--to=fengguang.wu@intel.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=srostedt@redhat.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