From: mulyadi.santosa@gmail.com (Mulyadi Santosa)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Ftracing in kernel
Date: Tue, 22 Feb 2011 11:56:00 +0700 [thread overview]
Message-ID: <AANLkTimgrGnU3LGO5LPbZMtU754JanR-ZUrbGyWAULub@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimQy+CHNam9bCtzh2BWOrODTfPOMzQfpz_H6TSV@mail.gmail.com>
On Tue, Feb 22, 2011 at 01:08, Erlon Cruz <sombrafam@gmail.com> wrote:
> Hmm...interesting guess. I made this change, declaring all functions
> as non static and the trace worked on then. Sweet! What made me get
> confused is that before this change, some of the functions traced
> correctly with ftrace were static.
Congrats :) Well, perhaps it is something related to symbol
lookup...but all in all, it's a good note for all of us.....
--
regards,
Mulyadi Santosa
Freelance Linux trainer and consultant
blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com
prev parent reply other threads:[~2011-02-22 4:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTinLPF-gQkh99bi1hNd+84T-H07YZMytZWu=vjsY@mail.gmail.com>
2011-02-21 13:34 ` Ftracing in kernel Erlon Cruz
2011-02-21 17:29 ` Mulyadi Santosa
2011-02-21 18:08 ` Erlon Cruz
2011-02-22 4:56 ` Mulyadi Santosa [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=AANLkTimgrGnU3LGO5LPbZMtU754JanR-ZUrbGyWAULub@mail.gmail.com \
--to=mulyadi.santosa@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).