perf-timechart(1) ================= NAME ---- perf-timechart - Tool to visualize total system behavior during a workload SYNOPSIS -------- [verse] 'perf timechart' [] {record} [] DESCRIPTION ----------- There are two variants of perf timechart: 'perf timechart record ' 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=:: 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=:: 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=:: 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=:: 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='h' value='nds-private-remove'/>
context:
space:
mode:
authorThomas Gleixner <tglx@linutronix.de>2017-01-31 23:58:38 +0100
committerIngo Molnar <mingo@kernel.org>2017-02-01 08:37:27 +0100
commitdd86e373e09fb16b83e8adf5c48c421a4ca76468 (patch)
tree55703c2ea8584e303e342090614e0aab3509ab21 /net/ceph/buffer.c
parent0b3589be9b98994ce3d5aeca52445d1f5627c4ba (diff)
perf/x86/intel/rapl: Make package handling more robust
The package management code in RAPL relies on package mapping being available before a CPU is started. This changed with: 9d85eb9119f4 ("x86/smpboot: Make logical package management more robust") because the ACPI/BIOS information turned out to be unreliable, but that left RAPL in broken state. This was not noticed because on a regular boot all CPUs are online before RAPL is initialized. A possible fix would be to reintroduce the mess which allocates a package data structure in CPU prepare and when it turns out to already exist in starting throw it away later in the CPU online callback. But that's a horrible hack and not required at all because RAPL becomes functional for perf only in the CPU online callback. That's correct because user space is not yet informed about the CPU being onlined, so nothing caan rely on RAPL being available on that particular CPU. Move the allocation to the CPU online callback and simplify the hotplug handling. At this point the package mapping is established and correct. This also adds a missing check for available package data in the event_init() function. Reported-by: Yasuaki Ishimatsu <yasu.isimatu@gmail.com> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com> Cc: Arnaldo Carvalho de Melo <acme@redhat.com> Cc: Jiri Olsa <jolsa@redhat.com> Cc: Linus Torvalds <torvalds@linux-foundation.org> Cc: Peter Zijlstra <peterz@infradead.org> Cc: Sebastian Siewior <bigeasy@linutronix.de> Cc: Stephane Eranian <eranian@google.com> Cc: Vince Weaver <vincent.weaver@maine.edu> Fixes: 9d85eb9119f4 ("x86/smpboot: Make logical package management more robust") Link: http://lkml.kernel.org/r/20170131230141.212593966@linutronix.de Signed-off-by: Ingo Molnar <mingo@kernel.org>
Diffstat (limited to 'net/ceph/buffer.c')