perf-timechart(1)
=================

NAME
----
perf-timechart - Tool to visualize total system behavior during a workload

SYNOPSIS
--------
[verse]
'perf timechart' [<timechart options>] {record} [<record options>]

DESCRIPTION
-----------
There are two variants of perf timechart:

  'perf timechart record <command>' to record the system level events
  of an arbitrary workload. By default timechart records only scheduler
  and CPU events (task switches, running times, CPU power states, etc),
  but it's possible to record IO (disk, network) activity using -I argument.

  'perf timechart' to turn a trace into a Scalable Vector Graphics file,
  that can be viewed with popular SVG viewers such as 'Inkscape'. Depending
  on the events in the perf.data file, timechart will contain scheduler/cpu
  events or IO events.

  In IO mode, every bar has two charts: upper and lower.
  Upper bar shows incoming events (disk reads, ingress network packets).
  Lower bar shows outgoing events (disk writes, egress network packets).
  There are also poll bars which show how much time application spent
  in poll/epoll/select syscalls.

TIMECHART OPTIONS
-----------------
-o::
--output=::
        Select the output file (default: output.svg)
-i::
--input=::
        Select the input file (default: perf.data unless stdin is a fifo)
-w::
--width=::
        Select the width of the SVG file (default: 1000)
-P::
--power-only::
        Only output the CPU power section of the diagram
-T::
--tasks-only::
        Don't output processor state transitions
-p::
--process::
        Select the processes to display, by name or PID

--symfs=<directory>::
        Look for files with symbols relative to this directory.
-n::
--proc-num::
        Print task info for at least given number of tasks.
-t::
--topology::
        Sort CPUs according to topology.
--highlight=<duration_nsecs|task_name>::
	Highlight tasks (using different color) that run more than given
	duration or tasks with given name. If number is given it's interpreted
	as number of nanoseconds. If non-numeric string is given it's
	interpreted as task name.
--io-skip-eagain::
	Don't draw EAGAIN IO events.
--io-min-time=<nsecs>::
	Draw small events as if they lasted min-time. Useful when you need
	to see very small and fast IO. It's possible to specify ms or us
	suffix to specify time in milliseconds or microseconds.
	Default value is 1ms.
--io-merge-dist=<nsecs>::
	Merge events that are merge-dist nanoseconds apart.
	Reduces number of figures on the SVG and makes it more render-friendly.
	It's possible to specify ms or us suffix to specify time in
	milliseconds or microseconds.
	Default value is 1us.

RECORD OPTIONS
--------------
-P::
--power-only::
        Record only power-related events
-T::
--tasks-only::
        Record only tasks-related events
-I::
--io-only::
        Record only io-related events
-g::
--callchain::
        Do call-graph (stack chain/backtrace) recording

EXAMPLES
--------

$ perf timechart record git pull

  [ perf record: Woken up 13 times to write data ]
  [ perf record: Captured and wrote 4.253 MB perf.data (~185801 samples) ]

$ perf timechart

  Written 10.2 seconds of trace to output.svg.

Record system-wide timechart:

  $ perf timechart record

  then generate timechart and highlight 'gcc' tasks:

  $ perf timechart --highlight gcc

Record system-wide IO events:

  $ perf timechart record -I

  then generate timechart:

  $ perf timechart

SEE ALSO
--------
linkperf:perf-record[1]
 name='id' value='79c6f448c8b79c321e4a1f31f98194e4f6b6cae7'/><table><tr><td colspan='2'/></tr><tr><td class='label'>context:</td><td class='ctrl'><select name='context' onchange='this.form.submit();'><option value='1'>1</option><option value='2'>2</option><option value='3' selected='selected'>3</option><option value='4'>4</option><option value='5'>5</option><option value='6'>6</option><option value='7'>7</option><option value='8'>8</option><option value='9'>9</option><option value='10'>10</option><option value='15'>15</option><option value='20'>20</option><option value='25'>25</option><option value='30'>30</option><option value='35'>35</option><option value='40'>40</option></select></td></tr><tr><td class='label'>space:</td><td class='ctrl'><select name='ignorews' onchange='this.form.submit();'><option value='0' selected='selected'>include</option><option value='1'>ignore</option></select></td></tr><tr><td class='label'>mode:</td><td class='ctrl'><select name='dt' onchange='this.form.submit();'><option value='0' selected='selected'>unified</option><option value='1'>ssdiff</option><option value='2'>stat only</option></select></td></tr><tr><td/><td class='ctrl'><noscript><input type='submit' value='reload'/></noscript></td></tr></table></form></div><table summary='commit info' class='commit-info'>
<tr><th>author</th><td>Steven Rostedt (VMware) &lt;rostedt@goodmis.org&gt;</td><td class='right'>2017-01-30 19:27:10 -0500</td></tr>
<tr><th>committer</th><td>Steven Rostedt (VMware) &lt;rostedt@goodmis.org&gt;</td><td class='right'>2017-01-31 09:13:49 -0500</td></tr>
<tr><th>commit</th><td colspan='2' class='oid'><a href='/cgit.cgi/linux/net-next.git/commit/net/kcm/Kconfig?h=nds-private-remove&amp;id=79c6f448c8b79c321e4a1f31f98194e4f6b6cae7'>79c6f448c8b79c321e4a1f31f98194e4f6b6cae7</a> (<a href='/cgit.cgi/linux/net-next.git/patch/net/kcm/Kconfig?id=79c6f448c8b79c321e4a1f31f98194e4f6b6cae7'>patch</a>)</td></tr>
<tr><th>tree</th><td colspan='2' class='oid'><a href='/cgit.cgi/linux/net-next.git/tree/?h=nds-private-remove&amp;id=79c6f448c8b79c321e4a1f31f98194e4f6b6cae7'>370efda701f03cccf21e02bb1fdd3b852547d75c</a> /<a href='/cgit.cgi/linux/net-next.git/tree/net/kcm/Kconfig?h=nds-private-remove&amp;id=79c6f448c8b79c321e4a1f31f98194e4f6b6cae7'>net/kcm/Kconfig</a></td></tr>
<tr><th>parent</th><td colspan='2' class='oid'><a href='/cgit.cgi/linux/net-next.git/commit/net/kcm/Kconfig?h=nds-private-remove&amp;id=0c744ea4f77d72b3dcebb7a8f2684633ec79be88'>0c744ea4f77d72b3dcebb7a8f2684633ec79be88</a> (<a href='/cgit.cgi/linux/net-next.git/diff/net/kcm/Kconfig?h=nds-private-remove&amp;id=79c6f448c8b79c321e4a1f31f98194e4f6b6cae7&amp;id2=0c744ea4f77d72b3dcebb7a8f2684633ec79be88'>diff</a>)</td></tr></table>
<div class='commit-subject'>tracing: Fix hwlat kthread migration</div><div class='commit-msg'>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) &lt;rostedt@goodmis.org&gt;
</div><div class='diffstat-header'><a href='/cgit.cgi/linux/net-next.git/diff/?h=nds-private-remove&amp;id=79c6f448c8b79c321e4a1f31f98194e4f6b6cae7'>Diffstat</a> (limited to 'net/kcm/Kconfig')</div><table summary='diffstat' class='diffstat'>