forked from Minki/linux
b639409704
Clarify in the documentation that 'perf mem report' reports use-latency, not load/store-latency on Intel systems. This often causes confusion with users. Signed-off-by: Andi Kleen <ak@linux.intel.com> Cc: Stephane Eranian <eranian@google.com> Link: http://lkml.kernel.org/r/1393596135-4227-2-git-send-email-andi@firstfloor.org Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
53 lines
1.3 KiB
Plaintext
53 lines
1.3 KiB
Plaintext
perf-mem(1)
|
|
===========
|
|
|
|
NAME
|
|
----
|
|
perf-mem - Profile memory accesses
|
|
|
|
SYNOPSIS
|
|
--------
|
|
[verse]
|
|
'perf mem' [<options>] (record [<command>] | report)
|
|
|
|
DESCRIPTION
|
|
-----------
|
|
"perf mem -t <TYPE> record" runs a command and gathers memory operation data
|
|
from it, into perf.data. Perf record options are accepted and are passed through.
|
|
|
|
"perf mem -t <TYPE> report" displays the result. It invokes perf report with the
|
|
right set of options to display a memory access profile.
|
|
|
|
Note that on Intel systems the memory latency reported is the use-latency,
|
|
not the pure load (or store latency). Use latency includes any pipeline
|
|
queueing delays in addition to the memory subsystem latency.
|
|
|
|
OPTIONS
|
|
-------
|
|
<command>...::
|
|
Any command you can specify in a shell.
|
|
|
|
-t::
|
|
--type=::
|
|
Select the memory operation type: load or store (default: load)
|
|
|
|
-D::
|
|
--dump-raw-samples=::
|
|
Dump the raw decoded samples on the screen in a format that is easy to parse with
|
|
one sample per line.
|
|
|
|
-x::
|
|
--field-separator::
|
|
Specify the field separator used when dump raw samples (-D option). By default,
|
|
The separator is the space character.
|
|
|
|
-C::
|
|
--cpu-list::
|
|
Restrict dump of raw samples to those provided via this option. Note that the same
|
|
option can be passed in record mode. It will be interpreted the same way as perf
|
|
record.
|
|
|
|
SEE ALSO
|
|
--------
|
|
linkperf:perf-record[1], linkperf:perf-report[1]
|