1. 02 Feb, 2018 1 commit
  2. 12 Jan, 2018 1 commit
  3. 19 Dec, 2017 1 commit
  4. 01 Dec, 2017 1 commit
  5. 18 Oct, 2017 1 commit
  6. 13 Oct, 2017 1 commit
  7. 03 Jul, 2017 1 commit
    • Jochen Eisinger's avatar
      Reland "Switch tracing to use v8::TracingController" · cc59f8b1
      Jochen Eisinger authored
      Original change's description:
      > Switch tracing to use v8::TracingController
      >
      > BUG=v8:6511
      > R=fmeawad@chromium.org
      >
      > Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng
      > Change-Id: I4961e4b61a9ddc98385ed97c3ffcbcaef2d9cba7
      > Reviewed-on: https://chromium-review.googlesource.com/543144
      > Commit-Queue: Jochen Eisinger <jochen@chromium.org>
      > Reviewed-by: Fadi Meawad <fmeawad@chromium.org>
      > Cr-Commit-Position: refs/heads/master@{#46307}
      
      BUG=v8:6511
      TBR=fmeawad@chromium.org
      
      Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng;master.tryserver.v8:v8_linux64_tsan_rel
      Change-Id: Ide32b409248dfd466e7c0bae1d8ae61d6a955d98
      Reviewed-on: https://chromium-review.googlesource.com/558865
      Commit-Queue: Jochen Eisinger <jochen@chromium.org>
      Reviewed-by: 's avatarJochen Eisinger <jochen@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#46381}
      cc59f8b1
  8. 29 Jun, 2017 2 commits
  9. 30 May, 2017 1 commit
  10. 29 Mar, 2017 1 commit
  11. 12 Jan, 2017 1 commit
  12. 15 Dec, 2016 1 commit
  13. 07 Dec, 2016 1 commit
    • lpy's avatar
      [Tracing] Implement IC statistics in tracing. · 0a3c8fc3
      lpy authored
      This patch introduces:
      
      1. ICStats class to store ic statistics items produced by V8,
      2. A disabled by default tracing category v8.ic_stats,
      3. An trace event V8.ICStats that contains ic statistics items in args,
      
      We store ic statistics items in an array until the array is full to reduce
      the number of trace events.
      
      TBR=jkummerow@chromium.org,ishell@chromium.org
      
      Review-Url: https://codereview.chromium.org/2503183002
      Cr-Commit-Position: refs/heads/master@{#41559}
      0a3c8fc3
  14. 06 Dec, 2016 1 commit
  15. 09 Nov, 2016 1 commit
  16. 08 Nov, 2016 1 commit
    • lpy's avatar
      [Tracing] Use TracingCategoryObserver in gc statistics · 7d28301d
      lpy authored
      This patch is a follow-up patch to enable gc statistics to use
      TracingCategoryObserver.
      
      Previously we need to pass --track_gc_object_stats to v8 if we want to enable
      gc statistics in tracing. In this patch, we introducce an integer flag
      FLAG_gc_stats, and FLAG_track_gc_object_stats and FLAG_trace_gc_object_stats
      will set it to 0x01, tracing will set it to 0x10 when we start tracing and
      reset the bit when we stop tracing.
      
      BUG=v8:5590
      
      Review-Url: https://codereview.chromium.org/2459903003
      Cr-Commit-Position: refs/heads/master@{#40817}
      7d28301d
  17. 07 Nov, 2016 1 commit
  18. 05 Nov, 2016 1 commit
  19. 04 Nov, 2016 2 commits
  20. 03 Nov, 2016 3 commits
  21. 28 Oct, 2016 2 commits
    • lpy's avatar
      [Tracing] Implement TracingCategoryObserver. · 6df8096a
      lpy authored
      This patch implements TracingCategoryObserver to set global flag when a V8
      specific category is enabled. Previously, we set a global flag each time when we
      encounter a top level trace event, and use it as a global check. With this
      patch, we can set a group of flags when tracing is enabled; besides, we make
      V8 tracing feature use V8 flags instead of defining its own flag in a messy way.
      
      With this patch, whatever V8 flag we want to imply in tracing, we define another
      integer flag, and the original V8 flag will set it to 0x01 when passing by
      commandline, tracing will set it to 0x10 when we start tracing and reset the bit
      when we stop tracing.
      
      Review-Url: https://codereview.chromium.org/2436273002
      Cr-Commit-Position: refs/heads/master@{#40659}
      6df8096a
    • lpy's avatar
      [Tracing] Fix inaccurate timer calculation in runtime statistics. · 92d9a56a
      lpy authored
      Previously we reset runtime counters and dump them when we enter, exit top level
      trace events respectively. However, there is gap between two top level trace
      events and runtime counters may be activated, resetting the counters makes the
      accumulated time inaccurate, and we may end up with negative time due to the
      nature of how we accumulate time.
      
      This patch fixes this problem by only resetting counters when there's no
      counters active, and before dump counters, we traverse current active counters
      to calculate their time, and then restart their timer.
      
      BUG=chromium:658145
      
      Review-Url: https://codereview.chromium.org/2457523002
      Cr-Commit-Position: refs/heads/master@{#40653}
      92d9a56a
  22. 19 Oct, 2016 1 commit
  23. 12 Oct, 2016 1 commit
  24. 06 Oct, 2016 1 commit
  25. 27 Sep, 2016 2 commits
  26. 26 Sep, 2016 1 commit
  27. 22 Sep, 2016 1 commit
  28. 19 Sep, 2016 1 commit
  29. 08 Sep, 2016 1 commit
  30. 05 Sep, 2016 1 commit
    • fmeawad's avatar
      [RuntimeCallStats] Move tracing runtime instrumentation closer to the original version. · e5ba156d
      fmeawad authored
      After we landed the tracing runtime call stats, which gave
      us a lot of V8 insight in tracing, we noticed that there is
      some arising issues and discrepancies.
      
      Issues include:
      Missing trace events, that happened due to
      transforming those trace events into runtime calls
      
      Discrepancies include:
      Missing categories in Runtime call stats like GC,
      because we are not handling the Scoped runtime calls
      properly in the tracing version.
      
      To reduce/eliminate those issue, we are taking a small
      step back. We are unifying the RuntimeStats code and
      using the original one. That would allow us to use all
      the original probes but emit trace events from them.
      We are also putting back the trace-events in their place.
      
      The output from both system should be intact (Except of
      the addition of the missing trace-events).
      
      Also as a byproduct, we are reducing the number of context
      scopes by half since we are using the same scope as
      runtime call stats.
      
      As a follow up to this CL, we will address the non-scoped
      Runtime Call Stats (mainly in GC).
      BUG=642373
      
      Review-Url: https://codereview.chromium.org/2296243002
      Cr-Commit-Position: refs/heads/master@{#39180}
      e5ba156d
  31. 26 Aug, 2016 1 commit
  32. 10 Aug, 2016 1 commit
  33. 08 Aug, 2016 1 commit
  34. 05 Aug, 2016 1 commit