1. 21 5月, 2014 2 次提交
  2. 16 4月, 2014 2 次提交
  3. 24 2月, 2014 1 次提交
  4. 18 2月, 2014 1 次提交
    • J
      perf tools: Add call-graph option support into .perfconfig · eb853e80
      Jiri Olsa 提交于
      Adding call-graph option support into .perfconfig file, so it's now
      possible use call-graph option like:
      
        [top]
              call-graph = fp
      
        [record]
              call-graph = dwarf,8192
      
      Above options ONLY setup the unwind method. To enable perf record/top to
      actually use it the command line option -g/-G must be specified.
      
      The --call-graph option overloads .perfconfig setup.
      
      Assuming above configuration:
      
        $ perf record -g ls
        - enables dwarf unwind with user stack size dump 8192 bytes
      
        $ perf top -G
        - enables frame pointer unwind
      
        $ perf record --call-graph=fp ls
        - enables frame pointer unwind
      
        $ perf top --call-graph=dwarf,4096 ls
        - enables dwarf unwind with user stack size dump 4096 bytes
      Signed-off-by: NJiri Olsa <jolsa@redhat.com>
      Cc: Adrian Hunter <adrian.hunter@intel.com>
      Cc: Andi Kleen <andi@firstfloor.org>
      Cc: Corey Ashford <cjashfor@linux.vnet.ibm.com>
      Cc: David Ahern <dsahern@gmail.com>
      Cc: Ingo Molnar <mingo@elte.hu>
      Cc: Namhyung Kim <namhyung@kernel.org>
      Cc: Paul Mackerras <paulus@samba.org>
      Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
      Link: http://lkml.kernel.org/r/1391427883-13443-2-git-send-email-jolsa@redhat.comSigned-off-by: NArnaldo Carvalho de Melo <acme@redhat.com>
      eb853e80
  5. 16 1月, 2014 1 次提交
  6. 13 1月, 2014 2 次提交
  7. 20 12月, 2013 1 次提交
  8. 19 12月, 2013 2 次提交
  9. 28 11月, 2013 2 次提交
  10. 15 11月, 2013 1 次提交
  11. 13 11月, 2013 1 次提交
  12. 12 11月, 2013 3 次提交
  13. 06 11月, 2013 1 次提交
    • J
      perf tools: Check maximum frequency rate for record/top · 714647bd
      Jiri Olsa 提交于
      Adding the check for maximum allowed frequency rate defined in following
      file:
      
        /proc/sys/kernel/perf_event_max_sample_rate
      
      When we cross the maximum value we fail and display detailed error
      message with advise.
      
        $ perf record -F 3000 ls
        Maximum frequency rate (2000) reached.
        Please use -F freq option with lower value or consider
        tweaking /proc/sys/kernel/perf_event_max_sample_rate.
      
      In case user does not specify the frequency and the default value cross
      the maximum, we display warning and set the frequency value to the
      current maximum.
      
        $ perf record ls
        Lowering default frequency rate to 2000.
        Please consider tweaking /proc/sys/kernel/perf_event_max_sample_rate.
      
      Same messages are used for 'perf top'.
      Signed-off-by: NJiri Olsa <jolsa@redhat.com>
      Cc: Adrian Hunter <adrian.hunter@intel.com>
      Cc: Corey Ashford <cjashfor@linux.vnet.ibm.com>
      Cc: David Ahern <dsahern@gmail.com>
      Cc: Frederic Weisbecker <fweisbec@gmail.com>
      Cc: Ingo Molnar <mingo@elte.hu>
      Cc: Namhyung Kim <namhyung@kernel.org>
      Cc: Paul Mackerras <paulus@samba.org>
      Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
      Link: http://lkml.kernel.org/r/1383660887-1734-4-git-send-email-jolsa@redhat.comSigned-off-by: NArnaldo Carvalho de Melo <acme@redhat.com>
      714647bd
  14. 05 11月, 2013 1 次提交
  15. 04 11月, 2013 2 次提交
  16. 29 10月, 2013 2 次提交
  17. 24 10月, 2013 1 次提交
  18. 22 10月, 2013 4 次提交
  19. 09 10月, 2013 2 次提交
  20. 04 10月, 2013 2 次提交
  21. 30 8月, 2013 1 次提交
  22. 12 8月, 2013 2 次提交
  23. 08 8月, 2013 2 次提交
  24. 13 7月, 2013 1 次提交
    • G
      perf report/top: Add option to collapse undesired parts of call graph · b21484f1
      Greg Price 提交于
      For example, in an application with an expensive function implemented
      with deeply nested recursive calls, the default call-graph presentation
      is dominated by the different callchains within that function.  By
      ignoring these callees, we can collect the callchains leading into the
      function and compactly identify what to blame for expensive calls.
      
      For example, in this report the callers of garbage_collect() are
      scattered across the tree:
      
        $ perf report -d ruby 2>- | grep -m10 ^[^#]*[a-z]
            22.03%     ruby  [.] gc_mark
                       --- gc_mark
                          |--59.40%-- mark_keyvalue
                          |          st_foreach
                          |          gc_mark_children
                          |          |--99.75%-- rb_gc_mark
                          |          |          rb_vm_mark
                          |          |          gc_mark_children
                          |          |          gc_marks
                          |          |          |--99.00%-- garbage_collect
      
      If we ignore the callees of garbage_collect(), its callers are coalesced:
      
        $ perf report --ignore-callees garbage_collect -d ruby 2>- | grep -m10 ^[^#]*[a-z]
            72.92%     ruby  [.] garbage_collect
                       --- garbage_collect
                           vm_xmalloc
                          |--47.08%-- ruby_xmalloc
                          |          st_insert2
                          |          rb_hash_aset
                          |          |--98.45%-- features_index_add
                          |          |          rb_provide_feature
                          |          |          rb_require_safe
                          |          |          vm_call_method
      Signed-off-by: NGreg Price <price@mit.edu>
      Tested-by: NJiri Olsa <jolsa@redhat.com>
      Cc: David Ahern <dsahern@gmail.com>
      Cc: Ingo Molnar <mingo@redhat.com>
      Cc: Jiri Olsa <jolsa@redhat.com>
      Cc: Namhyung Kim <namhyung@kernel.org>
      Cc: Paul Mackerras <paulus@samba.org>
      Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
      Link: http://lkml.kernel.org/r/20130623031720.GW22203@biohazard-cafe.mit.edu
      Link: http://lkml.kernel.org/r/20130708115746.GO22203@biohazard-cafe.mit.edu
      Cc: Fengguang Wu <fengguang.wu@intel.com>
      [ remove spaces at beginning of line, reported by Fengguang Wu ]
      Signed-off-by: NArnaldo Carvalho de Melo <acme@redhat.com>
      b21484f1