Skip to content

V
V8
Switch branch/tag
  1. 22 Oct, 2014 1 commit
  3. 17 Oct, 2014 1 commit
  5. 08 Oct, 2014 1 commit
  7. 29 Sep, 2014 1 commit
  9. 29 Aug, 2014 1 commit
  11. 26 Aug, 2014 1 commit
  13. 04 Aug, 2014 1 commit
  15. 09 Jul, 2014 1 commit
  17. 07 Jul, 2014 1 commit
  19. 03 Jul, 2014 1 commit
  21. 02 Jul, 2014 1 commit
  23. 30 Jun, 2014 1 commit
  25. 24 Jun, 2014 1 commit
  27. 20 Jun, 2014 1 commit
  29. 05 Jun, 2014 1 commit
  31. 03 Jun, 2014 1 commit
  33. 29 Apr, 2014 1 commit
  35. 25 Apr, 2014 1 commit
  37. 24 Mar, 2014 1 commit
  39. 21 Mar, 2014 1 commit
  41. 12 Feb, 2014 1 commit
  43. 02 Jan, 2014 1 commit
  45. 01 Oct, 2013 1 commit
  47. 29 Aug, 2013 4 commits
  49. 26 Aug, 2013 2 commits
    • yurys@chromium.org's avatar
      Use signals for cpu profiling on Mac OS X · a29ceb7b
      yurys@chromium.org authored 
      A while ago in r2315 Mac OS X cpu profiler implementation was changed to pause sampled thread instead of sending SIGPROF signal. That was done because at that point profiler send the signal to the whole process and it was handled on a random thread. Now that signal-based implementation uses pthread_kill it may well be used on Mac OS X too.

BUG=v8:2814
R=bmeurer@chromium.org, svenpanne@chromium.org

Review URL: https://codereview.chromium.org/23115005

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@16320 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      a29ceb7b
    • yurys@chromium.org's avatar
      Support higher CPU profiler sampling rate on posix systems · 4db1f475
      yurys@chromium.org authored 
      New flag is added that allows to specify CPU profiler sampling rate in microseconds as command line argument. It was tested to work fine with 100us interval(currently it is 1ms). Default values are kept the same as in the current implementation. The new implementation is enabled only on POSIX platforms which use signals to collect samples. Other platforms that pause thread being sampled are to follow.

SIGPROF signals are now sent on the profiler event processor thread to make sure that the processing thread does fall far behind the sampling.

The patch is based on the previous one that was rolled out in r13851. The main difference is that the circular queue is not modified for now.

On Linux sampling for CPU profiler is initiated on the profiler event processor thread, other platforms to follow.

CPU profiler continues to use SamplingCircularQueue, we will probably replace it with a single sample buffer when Mac and Win ports support profiling on the event processing thread.

When --prof option is specified profiling is initiated either on the profiler event processor thread if CPU profiler is on or on the SignalSender thread as it used to be if no CPU profiles are being collected.

ProfilerEventsProcessor::ProcessEventsAndDoSample now waits in a tight loop, processing collected samples until sampling interval expires. To save CPU resources I'm planning to change that to use nanosleep as only one sample is expected in the queue at any point.

BUG=v8:2814
R=bmeurer@chromium.org

Review URL: https://codereview.chromium.org/21101002

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@16310 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      4db1f475
  51. 23 Aug, 2013 1 commit
  53. 09 Aug, 2013 1 commit
  55. 07 Aug, 2013 1 commit
  57. 31 Jul, 2013 1 commit
  59. 30 Jul, 2013 1 commit
  61. 29 Jul, 2013 2 commits
  63. 23 Jul, 2013 1 commit
    • yurys@chromium.org's avatar
      Fix call stack sampling for the case when native callback invokes JS function · 97f8f91b
      yurys@chromium.org authored 
      The SafeStackFrameIterator used by CPU profiler checked if Isolate::c_entry_fp is null and if it is not it would think that the control flow currently is in some native code. This assumption is wrong because the native code could have called a JS function but JSEntryStub would not reset c_entry_fp to NULL in that case. This CL adds a check in SafeStackFrameIterator::IsValidTop for the case when there is a JAVA_SCRIPT frame on top of EXIT frame.

Also this CL changes ExternalCallbackScope behavior to provide access to the whole stack of the scope objects instead of only top one. This allowed to provide exact callback names for those EXIT frames where external callbacks are called. Without this change it was possible only for the top most native call.

BUG=None
R=loislo@chromium.org, yangguo@chromium.org

Review URL: https://codereview.chromium.org/19775017

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@15832 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      97f8f91b
  65. 10 Jul, 2013 1 commit
  67. 05 Jul, 2013 1 commit
  69. 03 Jul, 2013 1 commit