tibeecompare

Application to compare execution traces.

pre-requisites

• SCons for the build system

build

./bootstrap.sh
./configure
make

required events

This tool requires a trace with the following events:

Standard LTTng events:

• sched_ttwu
• sched_switch
• sched_process_fork
• sched_process_exec
• sched_process_exit
• softirq_entry
• softirq_exit
• hrtimer_expire_entry
• hrtimer_expire_exit
• irq_handler_entry
• irq_handler_exit
• inet_sock_local_in
• inet_sock_local_out
• lttng_statedump_end
• lttng_statedump_process_state
• lttng_statedump_start

Custom events generated by lttng-profile and lttng-profile-modules:

• syscall_latency
• on_cpu_sample
• off_cpu_sample

usage

Create a database of executions:

source setenv.sh
src/build/tibeebuild --name [name] --begin [begin] --end [end] --trace [trace]

• name: Name to give to the executions found in the trace.
• begin: Name of the event indicating the beginning of an execution. Prefix with ust/ for userspace events or by kernel/ for kernel events.
• end: Name of the event indicating the end of an execution. Prefix with ust/ for userspace events or by kernel/ for kernel events.
• trace: Path to the trace to analyze. It is possible to specify multiple traces to analyze at once.

Create a comparison file to use with tracecompare:

src/report/tibeereport --name [name]

• name: Name of the executions to compare.