Reviewers: danno,
Description:
Support for the Linux 'perf report' and 'perf annotate' tools.
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.
[email protected]
BUG=
Please review this at https://codereview.chromium.org/70013002/
SVN Base: https://v8.googlecode.com/svn/branches/bleeding_edge
Affected files (+263, -2 lines):
M src/flag-definitions.h
M src/isolate.cc
M src/log-utils.h
M src/log.h
M src/log.cc
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
