From mboxrd@z Thu Jan  1 00:00:00 1970
From: mulyadi.santosa@gmail.com (Mulyadi Santosa)
Date: Tue, 22 Feb 2011 11:56:00 +0700
Subject: Ftracing in kernel
In-Reply-To: <AANLkTimQy+CHNam9bCtzh2BWOrODTfPOMzQfpz_H6TSV@mail.gmail.com>
References: <AANLkTinLPF-gQkh99bi1hNd+84T-H07YZMytZWu=vjsY@mail.gmail.com>
	<AANLkTim_VBv9NiAXw-zDQA41q++Dygqh1JVLCdMUgXPY@mail.gmail.com>
	<AANLkTikQRiThx5YQtd9PdY=0f4bhQBUx3AnNkaVc8N=U@mail.gmail.com>
	<AANLkTimQy+CHNam9bCtzh2BWOrODTfPOMzQfpz_H6TSV@mail.gmail.com>
Message-ID: <AANLkTimgrGnU3LGO5LPbZMtU754JanR-ZUrbGyWAULub@mail.gmail.com>
To: kernelnewbies@lists.kernelnewbies.org
List-Id: kernelnewbies.lists.kernelnewbies.org

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