linux-toradex.git/arch/microblaze/kernel/ftrace.c, branch v3.16.2

ftrace: Do not pass data to ftrace_dyn_arch_init

2014-03-07T15:06:14+00:00

As the data parameter is not really used by any ftrace_dyn_arch_init,
remove that from ftrace_dyn_arch_init. This also removes the addr
local variable from ftrace_init which is now unused.

Note the documentation was imprecise as it did not suggest to set
(*data) to 0.

Link: http://lkml.kernel.org/r/1393268401-24379-4-git-send-email-jslaby@suse.cz

Cc: Frederic Weisbecker 
Cc: Ingo Molnar 
Cc: linux-arch@vger.kernel.org
Signed-off-by: Jiri Slaby 
Signed-off-by: Steven Rostedt

ftrace: Pass retval through return in ftrace_dyn_arch_init()

2014-03-07T15:06:13+00:00

No architecture uses the "data" parameter in ftrace_dyn_arch_init() in any
way, it just sets the value to 0. And this is used as a return value
in the caller -- ftrace_init, which just checks the retval against
zero.

Note there is also "return 0" in every ftrace_dyn_arch_init.  So it is
enough to check the retval and remove all the indirect sets of data on
all archs.

Link: http://lkml.kernel.org/r/1393268401-24379-3-git-send-email-jslaby@suse.cz

Cc: linux-arch@vger.kernel.org
Signed-off-by: Jiri Slaby 
Signed-off-by: Steven Rostedt

microblaze: Fix coding style issues

2013-02-12T10:24:45+00:00

Fix coding style issues reported by checkpatch.pl.

Signed-off-by: Michal Simek

microblaze: Fix ftrace

2011-04-01T07:34:51+00:00

- Do not trace idle loop which takes a lot time
- Fix cache handling in generic ftrace code
- Do not trace lib functions ashldi3, ashrdi3, lshrdi3
  Functions are called from generic ftrace code which
  can't be traced

Signed-off-by: Michal Simek

microblaze: Fix ftrace_update_ftrace_func panic

2010-04-07T05:27:25+00:00

The Microblaze dynamic ftrace code assumes a call ordering that is not met
in all scenarios. Specifically, executing a command similar to:

  echo 105 > /sys/kernel/debug/tracing/set_ftrace_pid

before any other tracing-related commands results in a kernel panic:

  BUG: failure at arch/microblaze/kernel/ftrace.c:198/ftrace_update_ftrace_func()!

Recoding ftrace_update_ftrace_func() to use &ftrace_caller directly eliminates
the need to capture its address elsewhere (and thus rely on a particular call
sequence).

Signed-off-by: Steven J. Magnani 
Signed-off-by: Michal Simek

microblaze: ftrace: Add dynamic function graph tracer

2009-12-14T07:44:54+00:00

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:53+00:00

For more information look at Documentation/trace folder.

Signed-off-by: Michal Simek

microblaze: ftrace: Add dynamic trace support

2009-12-14T07:44:01+00:00

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