User Tools

Site Tools


realtime:documentation:howto:debugging:cyclictest-smi-ftrace

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
realtime:documentation:howto:debugging:cyclictest-smi-ftrace [2018/08/21 10:18]
ebugden [Cyclictest - SMI detection with function tracing] Update link
realtime:documentation:howto:debugging:cyclictest-smi-ftrace [2018/08/21 13:12]
ebugden Move to smi-latency folder
Line 29: Line 29:
 </​code> ​ </​code> ​
  
-The combination of options in this example is not appropriate for every test situation. More details about how to choose the right options for measuring a specific latency on a given system can be found in the Cyclictest documentation [[realtime:​documentation:​howto:​debugging:​cyclictest:​test-design:start|here]].+The combination of options in this example is not appropriate for every test situation. More details about how to choose the right options for measuring a specific latency on a given system can be found in the Cyclictest documentation [[realtime:​documentation:​howto:​tools:​cyclictest:​test-design#​option-selection|here]].
  
 <WRAP center round important 60%> <WRAP center round important 60%>
Line 35: Line 35:
 </​WRAP>​ </​WRAP>​
  
-Function tracing slows down the execution of the program, so the target latency will most likely be longer after enabling tracing. It is important to adjust for this additional overhead because otherwise the tracing may not break on the correct latency and the trace may not contain the latency that was supposed to be observed. More details about how to adjust the break trace limit can be found in the documentation about debugging using Cyclictest [[realtime:​documentation:​howto:​debugging:​cyclictest:​debugging#​measuring-the-tracing-overhead|here]].+Function tracing slows down the execution of the program, so the target latency will most likely be longer after enabling tracing. It is important to adjust for this additional overhead because otherwise the tracing may not break on the correct latency and the trace may not contain the latency that was supposed to be observed. More details about how to adjust the break trace limit can be found in the documentation about debugging using Cyclictest [[realtime:​documentation:​howto:​tools:​cyclictest:​tracing#​measuring-the-tracing-overhead|here]].
  
 ===== Analysis ===== ===== Analysis =====