1. 01 4月, 2011 1 次提交
    • M
      microblaze: Fix ftrace · 9e1491de
      Michal Simek 提交于
      - 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: NMichal Simek <monstr@monstr.eu>
      9e1491de
  2. 07 4月, 2010 1 次提交
    • S
      microblaze: Fix ftrace_update_ftrace_func panic · d2bf98e6
      Steven J. Magnani 提交于
      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: NSteven J. Magnani <steve@digidescorp.com>
      Signed-off-by: NMichal Simek <monstr@monstr.eu>
      d2bf98e6
  3. 14 12月, 2009 3 次提交
    • M
      microblaze: ftrace: Add dynamic function graph tracer · 4f911b0d
      Michal Simek 提交于
      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: NMichal Simek <monstr@monstr.eu>
      4f911b0d
    • M
      microblaze: ftrace: add function graph support · a0d3e665
      Michal Simek 提交于
      For more information look at Documentation/trace folder.
      Signed-off-by: NMichal Simek <monstr@monstr.eu>
      a0d3e665
    • M
      microblaze: ftrace: Add dynamic trace support · 7d241ff0
      Michal Simek 提交于
      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: NSteven Rostedt <rostedt@goodmis.org>
      Signed-off-by: NMichal Simek <monstr@monstr.eu>
      7d241ff0