> Where in this trace is there a latency spike? I could not see one. Hi John, For the 5.2.0-rt1 trace data set I believe the latency is with cyclicte-1935 at the end. If I just look at the "cyclicte-1935 ... finish_task_switch <-__schedule" lines then the delta-t's are mostly around 200us except for the last delta-t which is >5000us cyclicte-1935 1d...3.. 84243668us : uao_thread_switch <-__switch_to cyclicte-1935 1d...3.. 84249436us : finish_task_switch <-__schedule The actual cyclictest output is shown below: # ./cyclictest -S -m -n -p 99 -i 200 -h 700 -f -b 5000 # /dev/cpu_dma_latency set to 0us INFO: debugfs mountpoint: /sys/kernel/debug/tracing/ policy: fifo: loadavg: 5.55 1.84 0.66 11/136 1941 T: 0 ( 1934) P:99 I:200 C: 411188 Min: 30 Act: 30 Avg: 93 Max: 652 T: 1 ( 1935) P:99 I:200 C: 382925 Min: 47 Act: 5713 Avg: 123 Max: 5713 T: 2 ( 1936) P:99 I:200 C: 395011 Min: 40 Act: 40 Avg: 117 Max: 561 T: 3 ( 1937) P:99 I:200 C: 392379 Min: 36 Act: 36 Avg: 109 Max: 636 thanks, Paul
