realtime:documentation:howto:debugging:cyclictest:debugging
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Next revision Both sides next revision | ||
|
realtime:documentation:howto:debugging:cyclictest:debugging [2018/07/23 14:10] ebugden Improve phrasing |
realtime:documentation:howto:debugging:cyclictest:debugging [2018/07/24 13:03] ebugden [Cyclictest - Latency debugging with tracing] Remove questionnable relevant tracefs sentence |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Cyclictest - Latency debugging with tracing ====== | ====== Cyclictest - Latency debugging with tracing ====== | ||
| - | Tracing is useful when trying to determine the cause of a latency because it can reveal relevant details about execution. There are several options in Cyclictest that can be used to produce traces via Ftrace. These traces can then be consulted via tracefs. | + | Tracing is useful when trying to determine the cause of a latency because it can reveal relevant details about execution. There are several options in Cyclictest that can be used to produce traces via Ftrace. |
| ===== Break Trace Option ===== | ===== Break Trace Option ===== | ||
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
