summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJuri Lelli <juri.lelli@arm.com>2016-11-24 09:12:57 +0000
committerJuri Lelli <juri.lelli@arm.com>2016-11-25 08:21:17 +0000
commitf29ac171d487e33456668fcd5c9c9d77f5c61ca1 (patch)
treefd5aff3ba113ac4541d38e16f9237cde808cd7aa
parenteb3ca23d902c5cf470ac4e23ba466bd87c195804 (diff)
doc: add log header fields descriptions
Add descrition for newly introduced log header fiels (slack, c_duration, c_period and wu_lat). Signed-off-by: Juri Lelli <juri.lelli@arm.com> Acked-by: Vincent Guittot <vincent.guittot@linaro.org>
-rw-r--r--doc/tutorial.txt36
1 files changed, 27 insertions, 9 deletions
diff --git a/doc/tutorial.txt b/doc/tutorial.txt
index 78cd1fe..bb6734c 100644
--- a/doc/tutorial.txt
+++ b/doc/tutorial.txt
@@ -430,20 +430,38 @@ metrics are:
- run: time spent by the thread to execute the run events
- period: duration to execute the complte phase
- start/end : absolute start and end time of a phase. Same time base is used in
-ftrace
+ ftrace
- rel_st: start time of a phase relatively to the beg of the use case
+- slack: for periodic phases (phases that ends with a timer), time between the
+ end of last event and the end of the phase, e.g.
+
+ taskA ...|-- run5 --|- sleep5 -|-- run5--|..timer20.|-- run5 --|- sleep5 -|-- run6 --|.timer20.|
+ <--------------- period 20 --------------> <--------------- period 20 -------------->
+ <-slack5-> <slack4->
+
+ it can also be negative if the execution of a phases' events overshoots the
+ current period, e.g.
+
+ taskA ...|-- run5 --|- sleep5 -|------- run30 ------xxxxxxxxxx|
+ <--------------- period 20 -------------->
+ <slack-5>
+
+- c_duration: sum of the configured duration of run/runtime events
+- c_period: sum of the timer(s) period(s)
+- wu_lat: sum of wakeup latencies after timer events
Below is an extract of a log:
# Policy : SCHED_OTHER priority : 0
-#idx perf run period start end rel_st
-0 500000 34382 114492 175604833899 175604948391 785
-0 500000 29786 109863 175604948437 175605058300 115323
-0 500000 26977 107077 175605058336 175605165413 225223
-0 500000 28667 108771 175605165458 175605274229 332344
-0 500000 26644 106745 175605274274 175605381019 441160
-0 500000 26745 106867 175605381061 175605487928 547947
-0 500000 29513 109620 175605487974 175605597595 654860
+#idx perf run period start end rel_st slack c_duration c_period wu_lat
+ 0 92164 19935 98965 504549567051 504549666016 2443 78701 20000 100000 266
+ 0 92164 19408 99952 504549666063 504549766015 101455 80217 20000 100000 265
+ 0 92164 19428 99952 504549766062 504549866014 201454 80199 20000 100000 264
+ 0 92164 19438 99955 504549866060 504549966015 301452 80190 20000 100000 265
+ 0 92164 19446 99952 504549966061 504550066013 401453 80093 20000 100000 264
+ 0 92164 19415 99953 504550066060 504550166013 501452 80215 20000 100000 263
+ 0 92164 19388 99954 504550166059 504550266013 601451 80242 20000 100000 264
+ 0 92164 19444 99956 504550266060 504550366015 701452 80185 20000 100000 265
Some gnuplot files are also created to generate charts based on the log files
for each thread and for each kind of metrics. The format of the chart that