[DumpTable] Add Latency table dumping

This patch parse sched_process_latency events to produce a corresponding
table suitable for plotting.

Signed-off-by: Patrick Bellasi <derkling@gmail.com>
[DumpTable] Cosmetics

Signed-off-by: Patrick Bellasi <derkling@gmail.com>
[Plot] Add Latency tables plotting

This patch plots latency data reported by sched_process_latency events.

Signed-off-by: Patrick Bellasi <derkling@gmail.com>
[Plot] Plot Latency data for each scheduler

Latency events are generated by the core scheduler, thus this patch ensure
to plot them for each of the possible scheduling classes.

Signed-off-by: Patrick Bellasi <derkling@gmail.com>
[DumpTable] Dump Burst/Rounds tables just for CBS scheduling policy

The Burst and Rounds events are available just for traces generated using
the CBS scheduling class.

Signed-off-by: Patrick Bellasi <derkling@gmail.com>
[Plot] Add a statistical accumulator

This class provides an accumulator capable to compute rolling statistics
on a set of data. Each time a new sample is added to the accumulator, overall
statistics are updated.
A set of getter methods allows to get each specific statistics metrics on
the dataset loaded so far.

Signed-off-by: Patrick Bellasi <derkling@gmail.com>
[Plot] Add AVG and Ci99 intervals on Latency samples

Both Delay and Slice plots of the Latency graph are now decorated with
a graphical representation of the 99% confidence interval for the collected
samples.

Signed-off-by: Patrick Bellasi <derkling@gmail.com>
[DumpTable] Add support to tag CPU on filename

The script has been "converted" to be per SINGLE CPU, each table
produced by the script is now tagged with the CPU ID which is added
to its filename.
Tables produced by the script are also now named with "_table_" in
their filename, to better distinguish them wrt "_trace_" input data.

A single "all CPUs" event file is also produced the first time the
script is used.

Signed-off-by: Patrick Bellasi <derkling@gmail.com>
[Trace] Check for sandbox setup

Tests requires by default a properly configured Sandbox, a check has
been added at the beginning of the script to notify the user if a
sandbox of CPUs has not yet been configured.

Signed-off-by: Patrick Bellasi <derkling@gmail.com>
[Test] Report list of CPUs used for tests

Tests runs within a Sandbox, the CPUs used for test are now reported
in the test logfile.

Signed-off-by: Patrick Bellasi <derkling@gmail.com>
[Test] Update to test on multiple CPUs

The tests are now executed on all the CPUs of a configured Sandbox.
Thus, to precisely tune on which CPU a tast should be run, now the
Sandbox must be properly configured.

Signed-off-by: Patrick Bellasi <derkling@gmail.com>