1. 31 Jan, 2020 1 commit
    • Peter Marshall's avatar
      [tools] Add a VMState for Atomics.wait · e8ba5699
      Peter Marshall authored
      We will use this state in devtools via the inspector to indicate
      whether a thread is currently stuck polling in atomics.wait.
      
      VMState already distinguishes the important states we care about which
      are idle vs. running JS. We also want to know the state for
      atomics.wait(), which is commonly used in WebWorkers to poll the main
      page for work to do.
      
      This CL just adds and maintains the state and adds assertions in
      atomics tests. Another CL will emit inspector notifications when the
      VMState changes in a way that the inspector cares about.
      
      Re-flow comments as a drive-by cleanup.
      
      Bug: chromium:1025490
      Change-Id: I961051bfb846aa20454a56214310370ea8e47d1c
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2033168
      Commit-Queue: Peter Marshall <petermarshall@chromium.org>
      Reviewed-by: 's avatarYang Guo <yangguo@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#66071}
      e8ba5699
  2. 22 May, 2019 1 commit
  3. 21 May, 2019 1 commit
  4. 20 May, 2019 2 commits
  5. 17 May, 2019 2 commits
  6. 08 Jan, 2019 1 commit
  7. 10 Aug, 2017 1 commit
  8. 22 May, 2017 1 commit
  9. 13 May, 2016 1 commit
    • cbruni's avatar
      [counters] Annotate v8 with more runtime call counters. · 407d9fce
      cbruni authored
      By fully annotating the API with runtime counters we can properly measure
      how much time we spend in total in v8. When --runtime-call-stats is specified
      we now disable the fast-paths for callbacks to properly measure them.
      As a drive-by-fix this CL unifies the LOG messages in api.cc.
      Additionally we added missing timers to gain better resolution in the parser
      and callbacks.
      
      BUG=
      
      Review-Url: https://codereview.chromium.org/1923893002
      Cr-Commit-Position: refs/heads/master@{#36248}
      407d9fce
  10. 11 May, 2016 1 commit
  11. 09 Mar, 2016 1 commit
  12. 08 Mar, 2016 1 commit
  13. 04 Mar, 2016 1 commit
  14. 23 Feb, 2016 1 commit
    • cbruni's avatar
      [counters] Making runtime counters reentrant. · 5e468666
      cbruni authored
      So far counters did not work when they were reentrant and thus would lead to
      wrong bookkeeping of the counter stack. Using a separate stack-allocated linked
      list to track the timer stack solves this issue. This is a temporary workaround
      with the limitations of the counter system in mind. Eventually we will move to
      the trace-based system for these kind of statistics.
      
      BUG=v8:4770
      LOG=n
      
      Review URL: https://codereview.chromium.org/1695733002
      
      Cr-Commit-Position: refs/heads/master@{#34208}
      5e468666
  15. 18 Feb, 2016 1 commit
  16. 30 Sep, 2015 1 commit
  17. 16 Jul, 2014 1 commit
  18. 03 Jun, 2014 1 commit
  19. 29 Apr, 2014 1 commit
  20. 12 Feb, 2014 1 commit
  21. 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
  22. 24 Apr, 2013 1 commit
  23. 28 Jan, 2013 1 commit
  24. 28 Nov, 2012 1 commit
  25. 22 Nov, 2012 1 commit
  26. 19 Jul, 2012 1 commit
  27. 13 Jul, 2011 1 commit
  28. 11 Jul, 2011 1 commit
  29. 18 Mar, 2011 3 commits
  30. 07 Dec, 2010 3 commits
  31. 20 Oct, 2010 1 commit
  32. 08 Jul, 2010 1 commit
  33. 08 Apr, 2010 1 commit
  34. 07 Apr, 2010 1 commit