From: Francis Moreau <francis.moro@gmail.com>
To: linux-perf-users@vger.kernel.org
Subject: how to get a kernel callgraph starting from a syscall
Date: Thu, 21 Apr 2011 09:46:49 +0200 [thread overview]
Message-ID: <BANLkTikNDX4hYpLjgDnPx8SXFvsv8Syr9g@mail.gmail.com> (raw)
Hello,
Sorry if the question is dumb but I'm a bit lost about this.
I know that ftrace exists but I think that perf can do this too: I
have a userspace application which is calling a libc C function (read)
which ends up doing a sys_read.
For the sys_read, I'd like to see what's happening in the kernel by
displaying the call graph.
Can perf do that ?
If so, would it be possible to point me out the perf command to use ?
Thanks
--
Francis
next reply other threads:[~2011-04-21 7:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-21 7:46 Francis Moreau [this message]
2011-04-21 15:23 ` how to get a kernel callgraph starting from a syscall David Ahern
2011-04-21 18:48 ` Francis Moreau
2011-04-21 19:49 ` David Ahern
2011-04-21 20:07 ` Francis Moreau
2011-04-22 0:47 ` David Ahern
2011-04-22 5:29 ` Francis Moreau
2011-04-22 11:46 ` Francis Moreau
2011-04-23 8:40 ` Stefan Hajnoczi
2011-04-23 9:01 ` Francis Moreau
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=BANLkTikNDX4hYpLjgDnPx8SXFvsv8Syr9g@mail.gmail.com \
--to=francis.moro@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).