From: Jiri Olsa <jolsa@redhat.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
David Ahern <dsahern@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [BUG] perf probe can't insert return kprobe
Date: Fri, 9 Jan 2015 16:44:21 +0100 [thread overview]
Message-ID: <20150109154421.GA7849@krava.brq.redhat.com> (raw)
In-Reply-To: <20150109153056.GB4136@krava.brq.redhat.com>
On Fri, Jan 09, 2015 at 04:30:56PM +0100, Jiri Olsa wrote:
> On Sat, Jan 10, 2015 at 12:21:13AM +0900, Namhyung Kim wrote:
> > On Fri, Jan 09, 2015 at 03:55:39PM +0100, Jiri Olsa wrote:
> > > hi,
> > > I couldn't use following perf command to insert return probe:
> > >
> > > # perf probe -a fork_exit=do_fork%return
> > > Added new event:
> > > Failed to write event: Invalid argument
> > > Error: Failed to add events.
> > >
> > >
> > > I'm pretty sure I used this command before, so seems like
> > > it's broken. I can still use debugfs tracing interface to
> > > do that:
> > > # echo 'r:do_fork_entry do_fork' > kprobe_events
> > >
> > > I used Arnaldo's latest perf/core and FC20 kernel:
> > >
> > > # uname -a
> > > Linux krava 3.17.7-200.fc20.x86_64 #1 SMP Wed Dec 17 03:35:33 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
> > > # ./perf version
> > > perf version 3.18.g6a7d78
> > >
> >
> > Is it just return probe? Did it work for normal kprobes?
>
> yep, works for normal probes
>
> > Maybe it's related to the below:
> >
> > https://lkml.org/lkml/2014/12/31/15
> >
> > Have you check the acme/perf/urgent too?
>
> hum.. can't access lkml, I'll check, also with perf/urgent
neither helped..
jirka
next prev parent reply other threads:[~2015-01-09 15:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-09 14:55 Jiri Olsa
2015-01-09 15:03 ` Arnaldo Carvalho de Melo
2015-01-09 15:06 ` David Ahern
2015-01-09 15:04 ` David Ahern
2015-01-09 15:21 ` Namhyung Kim
2015-01-09 15:25 ` David Ahern
2015-01-09 15:30 ` Jiri Olsa
2015-01-09 15:44 ` Jiri Olsa [this message]
2015-01-10 9:51 ` Namhyung Kim
2015-01-12 11:00 ` Masami Hiramatsu
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=20150109154421.GA7849@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=acme@redhat.com \
--cc=dsahern@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=namhyung@kernel.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
all inboxes | Powered by JetHome®