linux/arch/microblaze/kernel/mcount.S, branch v3.2.51

microblaze: ftrace: Add dynamic function graph tracer

2009-12-14T07:44:54Z

This patch add support for dynamic function graph tracer. There is one my expactation that I can do flush_icache after all code modification. On microblaze is this safer than do flush for every entry. For icache is used name flush but correct should be invalidation - this will be fix in upcomming new cache implementaion and WB support. Signed-off-by: Michal Simek

microblaze: ftrace: add function graph support

2009-12-14T07:44:53Z

For more information look at Documentation/trace folder. Signed-off-by: Michal Simek

microblaze: ftrace: Add dynamic trace support

2009-12-14T07:44:01Z

With dynamic function tracer, by default, _mcount is defined as an "empty" function, it returns directly without any more action. When enabling it in user-space, it will jump to a real tracing function(ftrace_caller), and do the real job for us. Differ from the static function tracer, dynamic function tracer provides two functions ftrace_make_call()/ftrace_make_nop() to enable/disable the tracing of some indicated kernel functions(set_ftrace_filter). In the kernel version, there is only one "_mcount" string for every kernel function, so, we just need to match this one in mcount_regex of scripts/recordmcount.pl. For more information please look at code and Documentation/trace folder. Steven ACK that scripts/recordmcount.pl part. Acked-by: Steven Rostedt Signed-off-by: Michal Simek

microblaze: ftrace: enable HAVE_FUNCTION_TRACE_MCOUNT_TEST

2009-12-14T07:40:10Z

Implement MCOUNT_TEST in asm code - it is faster than use generic code Signed-off-by: Michal Simek

microblaze: ftrace: add static function tracer

2009-12-14T07:40:09Z

If -pg of gcc is enabled with CONFIG_FUNCTION_TRACER=y. a calling to _mcount will be inserted into each kernel function. so, there is a possibility to trace the kernel functions in _mcount. This patch add the specific _mcount support for static function tracing. by default, ftrace_trace_function is initialized as ftrace_stub(an empty function), so, the default _mcount will introduce very little overhead. after enabling ftrace in user-space, it will jump to a real tracing function and do static function tracing for us. Commit message from Wu Zhangjin Signed-off-by: Michal Simek