realtime:documentation:howto:tools:cyclictest:tracing
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Last revision Both sides next revision | ||
|
realtime:documentation:howto:tools:cyclictest:tracing [2022/01/19 19:56] bartwensley [Selecting Instrumentation] Cyclictest no longer configures ftrace (since rt-tests version 1.4) |
realtime:documentation:howto:tools:cyclictest:tracing [2022/01/19 20:00] bartwensley [Measuring the Tracing Overhead] Removed --ftrace option as it was removed from cyclictest in rt-tests version 1.4. |
||
|---|---|---|---|
| Line 39: | Line 39: | ||
| </code> | </code> | ||
| - | and after a couple hours a maximum latency of 130 us is detected. To measure the value of the maximum latency with the overhead from function tracing, the following Cyclictest command could be run: | + | and after a couple hours a maximum latency of 130 us is detected. To measure the value of the maximum latency with the overhead from function tracing, ftrace can be enabled and then the following Cyclictest command could be run: |
| <code bash> | <code bash> | ||
| - | cyclictest --mlockall --smp --priority=80 --interval=200 --distance=0 --breaktrace=2000 --ftrace | + | cyclictest --mlockall --smp --priority=80 --interval=200 --distance=0 --breaktrace=2000 --tracemark |
| </code> | </code> | ||
realtime/documentation/howto/tools/cyclictest/tracing.txt ยท Last modified: 2022/01/19 20:01 by bartwensley
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
