perf-mem(1) =========== NAME ---- perf-mem - Profile memory accesses SYNOPSIS -------- [verse] 'perf mem' [] (record [] | 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 ------- ...:: 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. SEE ALSO -------- linkperf:perf-record[1], linkperf:perf-report[1] git.cgi/linux/net-next.git/log/net/sched/cls_u32.c'>logtreecommitdiff
diff options
context:
space:
mode:
authorSteven Rostedt (VMware) <rostedt@goodmis.org>2017-01-30 19:27:10 -0500
committerSteven Rostedt (VMware) <rostedt@goodmis.org>2017-01-31 09:13:49 -0500
commit79c6f448c8b79c321e4a1f31f98194e4f6b6cae7 (patch)
tree370efda701f03cccf21e02bb1fdd3b852547d75c /net/sched/cls_u32.c
parent0c744ea4f77d72b3dcebb7a8f2684633ec79be88 (diff)
tracing: Fix hwlat kthread migration
The hwlat tracer creates a kernel thread at start of the tracer. It is pinned to a single CPU and will move to the next CPU after each period of running. If the user modifies the migration thread's affinity, it will not change after that happens. The original code created the thread at the first instance it was called, but later was changed to destroy the thread after the tracer was finished, and would not be created until the next instance of the tracer was established. The code that initialized the affinity was only called on the initial instantiation of the tracer. After that, it was not initialized, and the previous affinity did not match the current newly created one, making it appear that the user modified the thread's affinity when it did not, and the thread failed to migrate again. Cc: stable@vger.kernel.org Fixes: 0330f7aa8ee6 ("tracing: Have hwlat trace migrate across tracing_cpumask CPUs") Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Diffstat (limited to 'net/sched/cls_u32.c')