threeeye
bc1d038eac
Squashed backup commit (no shallow-clone history issues) of xiaomi-mt6833-dev/kernel_xiaomi_mt6833 (lineage-23.2 branch, upstream commit 9eece662e) plus all fixes applied to get everpal_defconfig building clean against a modern (GCC 15.2.0) toolchain -- see the previous commit message on the lineage-23.2 branch (also in this repo history is not available here since this is a squashed snapshot; full incremental history lives in the local DL380 checkout and the upstream GitHub remote). Upstream: https://github.com/xiaomi-mt6833-dev/kernel_xiaomi_mt6833 (lineage-23.2)
69 lines
1.7 KiB
Plaintext
69 lines
1.7 KiB
Plaintext
perf-mem(1)
|
|
===========
|
|
|
|
NAME
|
|
----
|
|
perf-mem - Profile memory accesses
|
|
|
|
SYNOPSIS
|
|
--------
|
|
[verse]
|
|
'perf mem' [<options>] (record [<command>] | report)
|
|
|
|
DESCRIPTION
|
|
-----------
|
|
"perf mem 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 report" displays the result. It invokes perf report with the
|
|
right set of options to display a memory access profile. By default, loads
|
|
and stores are sampled. Use the -t option to limit to loads or stores.
|
|
|
|
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,store)
|
|
|
|
-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.
|
|
|
|
-K::
|
|
--all-kernel::
|
|
Configure all used events to run in kernel space.
|
|
|
|
-U::
|
|
--all-user::
|
|
Configure all used events to run in user space.
|
|
|
|
--ldload::
|
|
Specify desired latency for loads event.
|
|
|
|
-p::
|
|
--phys-data::
|
|
Record/Report sample physical addresses
|
|
|
|
SEE ALSO
|
|
--------
|
|
linkperf:perf-record[1], linkperf:perf-report[1]
|