Skip to content

V
V8
Switch branch/tag
  1. 19 Jan, 2011 3 commits
  3. 04 Jan, 2011 2 commits
  5. 20 Dec, 2010 1 commit
  7. 15 Dec, 2010 1 commit
  9. 07 Dec, 2010 3 commits
  11. 25 Nov, 2010 1 commit
  13. 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
  15. 18 Oct, 2010 1 commit
  17. 02 Sep, 2010 1 commit
  19. 16 Aug, 2010 1 commit
  21. 13 Aug, 2010 1 commit
  23. 22 May, 2010 1 commit
  25. 19 May, 2010 1 commit
  27. 11 May, 2010 1 commit
  29. 07 Apr, 2010 1 commit
  31. 06 Apr, 2010 1 commit
  33. 25 Mar, 2010 1 commit
  35. 19 Mar, 2010 1 commit
  37. 17 Mar, 2010 3 commits
  39. 25 Jan, 2010 1 commit
  41. 21 Jan, 2010 1 commit
    • mikhail.naganov@gmail.com's avatar
      Fix issue 553: function frame is skipped in profile when compare stub is called. · 999e3fca
      mikhail.naganov@gmail.com authored 
      The problem appeared due to a fact that stubs doesn't create a stack
frame, reusing the stack frame of the caller function. When building
stack traces, the current function is retrieved from PC, and its
callees are retrieved by traversing the stack backwards. Thus, for
stubs, the stub itself was discovered via PC, and then stub's caller's
caller was retrieved from stack.

To fix this problem, a pointer to JSFunction object is now captured
from the topmost stack frame, and is saved into stack trace log
record. Then a simple heuristics is applied whether a referred
function should be added to decoded stack, or not, to avoid reporting
the same function twice (from PC and from the pointer.)

BUG=553
TEST=added to mjsunit/tools/tickprocessor

Review URL: http://codereview.chromium.org/546089

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@3673 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      999e3fca
  43. 13 Nov, 2009 1 commit
  45. 12 Nov, 2009 2 commits
  47. 23 Oct, 2009 1 commit
  49. 31 Jul, 2009 1 commit
  51. 01 Jul, 2009 1 commit
    • mikhail.naganov@gmail.com's avatar
      Reimplement profiler sampler on Mac OS X to get it working under Chromium. · 8318f5e5
      mikhail.naganov@gmail.com authored 
      Previous implementation of sampler for OS X was copied from the Linux one. But BSD (OS X) and Linux has a very important difference in signal handling. LinuxThreads doesn't support the notion of process-directed signals. So, the SIGPROF signal was directed to the thread that installed the handler---the V8 thread. But on BSD, signal handling is implemented according to POSIX spec, where process-directed signal is to be handled by an arbitrary selected thread. By a coincidence, in V8's sample shell and in Chromium's test shell, V8's thread was picked almost every time, so sampling seemed working. But not in case of Chromium.

So, I've changed the implementation of profiler sampler to use the same scheme as on Windows---a dedicated thread with high priority is used to periodically pause and sample V8's thread.

Review URL: http://codereview.chromium.org/147150

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@2315 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      8318f5e5
  53. 25 Jun, 2009 1 commit
  55. 24 Jun, 2009 2 commits
  57. 28 May, 2009 1 commit
  59. 25 May, 2009 2 commits