From: OSDepend <osdepend@gmail.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: linux-perf-users <linux-perf-users@vger.kernel.org>,
nelakurthi koteswararao <koteswararao18@gmail.com>
Subject: Re: Re: Fw: Re: Re: Howto make perf probe work
Date: Thu, 4 Apr 2013 01:28:34 +0800 [thread overview]
Message-ID: <201304040128323646722@gmail.com> (raw)
In-Reply-To: 201304021710591525728@gmail.com
Hi,
> > Or How can i add a exit tracepoint for handle_mm_fault()? so I can calculate the latency of that fault handle function?
> Try "perf probe -a entry=handle_mm_fault -a exit=handle_mm_fault%return"
That's works nicely for me!
Thanks a lot!!
> On Tue, 2 Apr 2013 17:11:01 +0800,
> >> For some reason, do_page_fault() is marked as __kprobe on some arch
> >> which means it cannot be probed.
> >
> > My kernel is runing on X86_64 arch, is there any chance for me to get the do_page_fault() entry/exit work?
> nope, AFAIK.
Is there any guide for us to decide which tracepoint (or other kernel symbol) canbe used, and which cannot?
For some of the kallsyms cannot be used directly. Such as do_raw_spin_lock.
perf probe -a test=do_raw_spin_lock
Fatal: Kernel symbol 'do_raw_spin_lock' not found - probe not added.
Best,
Chen
next prev parent reply other threads:[~2013-04-03 17:28 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 ` Fw: Re: " OSDepend
2013-04-02 4:36 ` Namhyung Kim
2013-04-02 9:11 ` OSDepend
2013-04-03 8:09 ` Namhyung Kim
2013-04-03 17:28 ` OSDepend [this message]
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=201304040128323646722@gmail.com \
--to=osdepend@gmail.com \
--cc=koteswararao18@gmail.com \
--cc=linux-perf-users@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).