linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: OSDepend <osdepend@gmail.com>
To: linux-perf-users <linux-perf-users@vger.kernel.org>
Cc: nelakurthi koteswararao <koteswararao18@gmail.com>
Subject: Fw: Re: Re: Howto make perf probe work
Date: Mon, 1 Apr 2013 23:24:41 +0800	[thread overview]
Message-ID: <201304012324395211298@gmail.com> (raw)
In-Reply-To: 201304012320294652937@gmail.com

>HI,
>Please enable kprobe_event config option in the kernel and build the same
>and boot the board using it. Then please try to add event using perf probe
>command

Thanks very much for your reply, and I already enable DEBUG_KPROBE_EVENT in kernel.
I did success in "perf probe handle_mm_fault".

But when i want to to "perf probe" other Kernel symbol, such as do_page_fault.
I came across other problems:
    Added new event:
    Failed to write event: Invalid argument
    Error: Failed to add events. (-1)
And when i type perf probe page_fault_entry:
    Kernel symbol 'page_fault_entry' not found.
    Error: Failed to add events. (-2)
Please notice that "do_page_fault" and "page_fault_entry" are all Kernel symbols, which canbe find in  "/proc/kallsyms", but not recorgonized by perf (or even kprobe).
Any idea for that?

Best,
Chen

>>On Sun, Mar 31, 2013 at 11:00 PM, OSDepend <osdepend@gmail.com> wrote:
>>Hi all,
>>        Is there any way to use perf probe to add new tracepoint like pagefault enter/exit?
>>        When I type perf probe fault:10
>>       I always get the error as follow:
>>                Debuginfo-analysis is not supported.
>>                Error: Failed to add events. (-38)
>>        What exactly i miss to get the perf probe work correctly?
>>Best,
>>Chen

  reply	other threads:[~2013-04-01 15:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-31 17:30 Howto make perf probe work OSDepend
     [not found] ` <CAGJbQddYW4-QZUvGpwCbmVhsvGEan5UkgRbXq+w4i+9Ob9vUrw@mail.gmail.com>
2013-04-01 15:20   ` OSDepend
2013-04-01 15:24     ` OSDepend [this message]
2013-04-02  4:36       ` Fw: Re: " Namhyung Kim
2013-04-02  9:11       ` OSDepend
2013-04-03  8:09         ` Namhyung Kim
2013-04-03 17:28         ` OSDepend
2013-04-04  6:05           ` Namhyung Kim

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=201304012324395211298@gmail.com \
    --to=osdepend@gmail.com \
    --cc=koteswararao18@gmail.com \
    --cc=linux-perf-users@vger.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;
as well as URLs for NNTP newsgroup(s).