From: David Ahern <dsahern@gmail.com>
To: Jiri Olsa <jolsa@redhat.com>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>,
Namhyung Kim <namhyung@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [BUG] perf probe can't insert return kprobe
Date: Fri, 09 Jan 2015 08:04:38 -0700 [thread overview]
Message-ID: <54AFEE06.1070000@gmail.com> (raw)
In-Reply-To: <20150109145539.GC14750@krava.brq.redhat.com>
On 1/9/15 7:55 AM, 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
>
If you want to bisect it the perf-probe command works for me on FC20,
3.17.7-200.fc20.x86_64 with perf from 3.12 (my local modified version is
based on 3.12).
David
next prev parent reply other threads:[~2015-01-09 15:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-09 14:55 [BUG] perf probe can't insert return kprobe 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 [this message]
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
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=54AFEE06.1070000@gmail.com \
--to=dsahern@gmail.com \
--cc=acme@redhat.com \
--cc=jolsa@redhat.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