1. 18 May, 2011 1 commit
  2. 29 Apr, 2011 1 commit
  3. 22 Feb, 2011 2 commits
    • mikhail.naganov@gmail.com's avatar
      Fix CPU profiling for Crankshaft. · 56788625
      mikhail.naganov@gmail.com authored
      The main issue was due to multiple recompilations of functions.  Now
      code objects are grouped by function using SFI object address.
      JSFunction objects are no longer tracked, instead we track SFI object
      moves. To pick a correct code version, we now sample return addresses
      instead of JSFunction addresses.
      
      tools/{linux|mac|windows}-tickprocessor scripts differentiate
      between code optimization states for the same function
      (using * and ~ prefixes introduced earlier).
      
      DevTools CPU profiler treats all variants of function code as
      a single function.
      
      ll_prof treats each optimized variant as a separate entry, because
      it can disassemble each one of them.
      
      tickprocessor.py not updated -- it is deprecated and will be removed.
      
      BUG=v8/1087,b/3178160
      TEST=all existing tests pass, including Chromium layout tests
      
      Review URL: http://codereview.chromium.org/6551011
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@6902 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      56788625
    • vitalyr@chromium.org's avatar
      grokdump: Simple windows minidump analysis on linux. · 25f2f21f
      vitalyr@chromium.org authored
      Analyses full minidump (.dmp) files.
      
      Shows the processor state at the point of exception including the
      stack of the active thread and the referenced objects in the V8
      heap. Code objects are disassembled and the addresses linked from the
      stack (pushed return addresses) are marked with "=>".
      
      Review URL: http://codereview.chromium.org/6312058
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@6896 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      25f2f21f
  4. 07 Dec, 2010 2 commits
  5. 28 Oct, 2010 1 commit
  6. 19 Oct, 2010 1 commit
    • vitalyr@chromium.org's avatar
      Support profiling based on linux kernel performance events. · e6b33bd2
      vitalyr@chromium.org authored
      Since 2.6.31 perf_events interface has been available in the
      kernel. There's a nice tool called "perf" (linux-2.6/tools/perf) that
      uses this interface and provides capabilities similar to oprofile. The
      simplest form of its usage is just dumping the raw log (trace) of
      events generated by the kernel. In this patch I'm adding a script
      (tools/ll_prof.py) to build profiles based on perf trace and our code
      log. All the heavy-lifting is done by perf. Compared to oprofile agent
      this approach does not require recompilation and supports code moving
      garbage collections.
      
      Expected usage is documented in the ll_prof's help. Basically one
      should run V8 under perf passing --ll-prof flag and then the produced
      logs can be analyzed by tools/ll_prof.py.
      
      The new --ll-prof flag enables logging of generated code object
      locations and names (like --log-code), and also of their bodies, which
      can be later disassembled and annotated by the script.
      
      Review URL: http://codereview.chromium.org/3831002
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@5663 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      e6b33bd2