kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: bskmohan@gmail.com (sri)
To: kernelnewbies@lists.kernelnewbies.org
Subject: how to get kernel functions calling stack/invokation ordert
Date: Fri, 1 Apr 2011 15:19:55 +0530	[thread overview]
Message-ID: <AANLkTinj4DA7SUhqUrxEBC0bwxYv9N8oBuN9xWufmr-g@mail.gmail.com> (raw)

Hi,

Is there a way to find, in the kernel src tree, which routine/function is
calling another function OR kernel function invocation stack order?
This would be helpful for me to know the various steps/functionalities
involved during executing something in kernel space.

-Sri-
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110401/dd23be1d/attachment-0001.html 

             reply	other threads:[~2011-04-01  9:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-01  9:49 sri [this message]
2011-04-01 10:03 ` how to get kernel functions calling stack/invokation ordert Daniel Baluta
2011-04-01 11:06   ` sri
2011-04-01 10:03 ` Daniel Baluta

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=AANLkTinj4DA7SUhqUrxEBC0bwxYv9N8oBuN9xWufmr-g@mail.gmail.com \
    --to=bskmohan@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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).