mirror of
https://github.com/team-infusion-developers/android_kernel_samsung_msm8976.git
synced 2024-11-01 10:33:27 +00:00
7a4ec93885
When analyzing perf data from hosts of other architecture than one of the local host it's useful to call objdump that is part of a toolchain for that architecture. Instead of calling regular objdump, call one that user specified in command line. Signed-off-by: Maciek Borzecki <maciek.borzecki@gmail.com> Acked-by: David Ahern <dsahern@gmail.com> Link: http://lkml.kernel.org/r/1346754750.16299.3.camel@localhost.localdomain Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
93 lines
2.1 KiB
Text
93 lines
2.1 KiB
Text
perf-annotate(1)
|
|
================
|
|
|
|
NAME
|
|
----
|
|
perf-annotate - Read perf.data (created by perf record) and display annotated code
|
|
|
|
SYNOPSIS
|
|
--------
|
|
[verse]
|
|
'perf annotate' [-i <file> | --input=file] [symbol_name]
|
|
|
|
DESCRIPTION
|
|
-----------
|
|
This command reads the input file and displays an annotated version of the
|
|
code. If the object file has debug symbols then the source code will be
|
|
displayed alongside assembly code.
|
|
|
|
If there is no debug info in the object, then annotated assembly is displayed.
|
|
|
|
OPTIONS
|
|
-------
|
|
-i::
|
|
--input=::
|
|
Input file name. (default: perf.data unless stdin is a fifo)
|
|
|
|
-d::
|
|
--dsos=<dso[,dso...]>::
|
|
Only consider symbols in these dsos.
|
|
-s::
|
|
--symbol=<symbol>::
|
|
Symbol to annotate.
|
|
|
|
-f::
|
|
--force::
|
|
Don't complain, do it.
|
|
|
|
-v::
|
|
--verbose::
|
|
Be more verbose. (Show symbol address, etc)
|
|
|
|
-D::
|
|
--dump-raw-trace::
|
|
Dump raw trace in ASCII.
|
|
|
|
-k::
|
|
--vmlinux=<file>::
|
|
vmlinux pathname.
|
|
|
|
-m::
|
|
--modules::
|
|
Load module symbols. WARNING: use only with -k and LIVE kernel.
|
|
|
|
-l::
|
|
--print-line::
|
|
Print matching source lines (may be slow).
|
|
|
|
-P::
|
|
--full-paths::
|
|
Don't shorten the displayed pathnames.
|
|
|
|
--stdio:: Use the stdio interface.
|
|
|
|
--tui:: Use the TUI interface Use of --tui requires a tty, if one is not
|
|
present, as when piping to other commands, the stdio interface is
|
|
used. This interfaces starts by centering on the line with more
|
|
samples, TAB/UNTAB cycles through the lines with more samples.
|
|
|
|
-C::
|
|
--cpu:: Only report samples for the list of CPUs provided. Multiple CPUs can
|
|
be provided as a comma-separated list with no space: 0,1. Ranges of
|
|
CPUs are specified with -: 0-2. Default is to report samples on all
|
|
CPUs.
|
|
|
|
--asm-raw::
|
|
Show raw instruction encoding of assembly instructions.
|
|
|
|
--source::
|
|
Interleave source code with assembly code. Enabled by default,
|
|
disable with --no-source.
|
|
|
|
--symfs=<directory>::
|
|
Look for files with symbols relative to this directory.
|
|
|
|
-M::
|
|
--disassembler-style=:: Set disassembler style for objdump.
|
|
|
|
--objdump=<path>::
|
|
Path to objdump binary.
|
|
|
|
SEE ALSO
|
|
--------
|
|
linkperf:perf-record[1], linkperf:perf-report[1]
|