From: "Li, Aubrey" <aubrey.li@linux.intel.com>
To: "Du, ChangbinX" <changbinx.du@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [HELP] How to use ftrace to learn how a function is ivoked?
Date: Thu, 03 Apr 2014 15:03:26 +0800 [thread overview]
Message-ID: <533D07BE.8070202@linux.intel.com> (raw)
In-Reply-To: <0C18FE92A7765D4EB9EE5D38D86A563A01AA980B@SHSMSX103.ccr.corp.intel.com>
On 2014/4/3 14:36, Du, ChangbinX wrote:
> Hi, All,
> I have a question for ftrace usage. It is that if I have a function A, then I want to
> know how function A is ivoked?
> I know ftrace can show me what sub-functions that A called by below steps:
> # echo function_graph > current_tracer
> # echo function_A > set_graph_function
> # cat trace
> Then a call stack will show what functions A has called. But sometimes I want to
> know how A is called. Is there a method to do this? Please help me!
dump_stack(), kprobe, AFAIK.
Thanks,
-Aubrey
prev parent reply other threads:[~2014-04-03 7:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 6:36 [HELP] How to use ftrace to learn how a function is ivoked? Du, ChangbinX
2014-04-03 7:03 ` Li, Aubrey [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=533D07BE.8070202@linux.intel.com \
--to=aubrey.li@linux.intel.com \
--cc=changbinx.du@intel.com \
--cc=linux-kernel@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