linux-kernel - Re: Ftracing in linux kernel

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1298662443.6376.20.camel@gandalf.stny.rr.com>
Date:	Fri, 25 Feb 2011 14:34:03 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Erlon Cruz <sombrafam@...il.com>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: Ftracing in linux kernel

On Mon, 2011-02-21 at 11:21 -0300, Erlon Cruz wrote:
> Hi folks,
> 
>    I've configured my kernel(2.6.35) to support ftrace*. Everything
> seems to be ok. After I mounted the debugfs folder I can find all
> tracing stuffs there. The problem is not of all functions on my module
> seems to be listed in the funtions supported for tracing. In the file
> available_filter_functions that suppose to list all functions traced,
> only show 4 or 5 functions of my module. Does anyone knows why some
> functions are not listed?

Are those functions inlined? If gcc inlines a function (regardless if
you say to or not) it will not be traced. If you want to trace them just
force them to not inline with "noinline".

-- Steve


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/