Skip to content

V
V8
Switch branch/tag
  1. 26 Feb, 2015 1 commit
  3. 10 Feb, 2015 1 commit
    • loislo's avatar
      Propagate DeoptInfo to cpu-profiler · 86cae163
      loislo authored 
      1) Deoptimizer::Reason was replaced with Deoptimizer::DeoptInfo
because it also has raw position. Also the old name clashes with DeoptReason enum.

2) c_entry_fp assignment call was added to EntryGenerator::Generate
So we can calculate sp and have a chance to record the stack for the deopting function.
btw it makes the test stable.

3) new kind of CodeEvents was added to cpu-profiler

4) GetDeoptInfo method was extracted from PrintDeoptLocation.
So it could be reused in cpu profiler.

BUG=452067
LOG=n

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

Cr-Commit-Position: refs/heads/master@{#26545}
      86cae163
  5. 15 Oct, 2014 1 commit
  7. 14 Oct, 2014 1 commit
  9. 16 Jul, 2014 1 commit
  11. 30 Jun, 2014 1 commit
  13. 13 Jun, 2014 1 commit
  15. 12 Jun, 2014 1 commit
  17. 10 Jun, 2014 1 commit
  19. 03 Jun, 2014 1 commit
  21. 22 May, 2014 1 commit
  23. 06 May, 2014 1 commit
  25. 30 Apr, 2014 1 commit
  27. 29 Apr, 2014 1 commit
  29. 04 Apr, 2014 2 commits
  31. 03 Apr, 2014 2 commits
  33. 18 Mar, 2014 1 commit
  35. 10 Mar, 2014 1 commit
  37. 31 Jan, 2014 1 commit
  39. 07 Jan, 2014 1 commit
  41. 25 Nov, 2013 1 commit
    • jarin@chromium.org's avatar
      Support for the Linux 'perf report' and 'perf annotate' tools. · 4e439deb
      jarin@chromium.org authored 
      In this change, the support comes in two flavours:

--perf_jit_prof - outputs the files in a new perf format that only works with a
patched perf tool (patch obtained from Stephane Eranian). Both 'perf report' and
'perf annotate' are supported (the file format also contains the machine code).

--perf_basic_prof - outputs the files in a format that the existing perf tool
can consume. Only 'perf report' is supported.

In both cases, we have to disable code compaction because the perf tool does not
understand code relocation. (We are told that code relocation should be
supported soon.)

Usage:

perf record -g d8 --perf_jit_prof --no_compact_code_space my.js
perf report

The change itself is straightforward - we simply listen to code events and
write an entry to a log file for every new piece of code.

I am not yet sure whether we should keep both versions or just one (and which
one). My hope is the reviewers can help here.

R=danno@chromium.org
BUG=

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

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@18034 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      4e439deb
  43. 10 Oct, 2013 1 commit
  45. 30 Sep, 2013 1 commit
  47. 29 Aug, 2013 2 commits
  49. 28 Aug, 2013 6 commits
  51. 23 Aug, 2013 1 commit
  53. 22 Aug, 2013 1 commit
  55. 29 Jul, 2013 1 commit
  57. 26 Jul, 2013 1 commit
    • loislo@chromium.org's avatar
      Logger: introduce abstract interface for CodeEvent listeners. · 141ada02
      loislo@chromium.org authored 
      New abstract class CodeEventListener was created.

CodeEventLogger which is the base class for Jit, LowLevel
and CodeAddressMap loggers was inherited from CodeEventListener.

CodeAddressMap class was moved to serializer.cc because serializer is the only user for it. Actually it collects code names and pushes them to the standard log as SnapshotCodeNameEvent. So I extracted this code into separate function CodeNameEvent. It happens that this method works only when Serializer serializes an object. So I added direct log call there.

CodeEventLogger class declaration was moved to the header
because CodeAddressMap needs it.
The code for the nested class CodeEventLogger::NameBuffer was left in the cc file.

CpuProfiler now is inherit CodeEventListener but not used
the loggers infrastructure yet due to the complex initialization schema. I'd like to fix that in a separate cl.

BUG=none
TEST=current test set.
R=yangguo@chromium.org, yurys@chromium.org

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

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@15911 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      141ada02
  59. 19 Jul, 2013 2 commits
  61. 18 Jul, 2013 1 commit