<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><br><br></div><div><br>On 21.11.2014, at 16:41, jp walters <<a href="mailto:mailinglistjp39@gmail.com">mailinglistjp39@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div>Which traces are you interested in? I can recreate the 3-task system easily enough, and I can capture /dev/litmus/log. I can also use feather trace to get /dev/litmus/sched_traceX data. </div></blockquote><div><br></div><div>Until we suspect a real bug in the kernel I'm mainly interested in sched_trace data. </div><br><blockquote type="cite"><div>Poking around the list, I've seen recommendations to use the following to parse out the sched_trace logs:</div><div><br></div><div><a href="https://github.com/brandenburg/sched-trace-tools">https://github.com/brandenburg/sched-trace-tools</a><br></div><div><br></div><div>I pulled that down, and using the job_stats tool on the output from st_trace, I'm left with plaintext data that looks like below (one for each CPU). I'm probably doing something wrong though.</div><div><br></div><div><div>root@ubuntu-qemu:~/non-script.data# cat simple0</div></div></blockquote><div><br></div><div>Make sure you give the tool all</div><div>per-CPU files together to analyze the complete trace. The data below looks like per-CPU data (huge gaps in the job sequence numbers).</div><br><blockquote type="cite"><div><div># Task, Job, Period, Response, DL Miss?, Lateness, Tardiness</div><div># task NAME=<unknown> PID=3802 COST=0 PERIOD=0 CPU=-1</div><div> 3802, 9, 0, 30657540, 0, -29342460, 0</div><div> 3802, 13, 0, 32616504, 0, -27383496, 0</div><div> 3802, 39, 0, 30793032, 0, -29206968, 0</div><div> 3802, 89, 0, 29259038, 0, -30740962, 0</div><div> 3802, 93, 0, 29860287, 0, -30139713, 0</div><div> 3802, 97, 0, 29485435, 0, -30514565, 0</div><div> 3802, 101, 0, 30333923, 0, -29666077, 0</div><div> 3802, 131, 0, 30122722, 0, -29877278, 0</div><div> 3802, 135, 0, 30649661, 0, -29350339, 0</div><div># task NAME=<unknown> PID=3801 COST=0 PERIOD=0 CPU=-1</div></div></blockquote><br><div>This looks totally ok. All jobs in this trace have zero tardiness / negative lateness and met their deadlines. I don't see a problem here. </div><div><br></div><div>- Björn </div></body></html>