Introduce fast/NMI safe accessor to clock tai for tracing. The Linux kernel tracing infrastructure has support for using different clocks to generate timestamps for trace events. Especially in TSN networks it's useful to have TAI as trace clock, because the application scheduling is done in accordance to the network time, which is based on TAI. With a tai trace_clock in place, it becomes very convenient to correlate network activity with Linux kernel application traces. Use the same implementation as ktime_get_boot_fast_ns() does by reading the monotonic time and adding the TAI offset. The same limitations as for the fast boot implementation apply. The TAI offset may change at run time e.g., by setting the time or using adjtimex() with an offset. However, these kind of offset changes are rare events. Nevertheless, the user has to be aware and deal with it in post processing. An alternative approach would be to use the same implementation as ktime_get_real_fast_ns() does. However, this requires to add an additional u64 member to the tk_read_base struct. This struct together with a seqcount is designed to fit into a single cache line on 64 bit architectures. Adding a new member would violate this constraint.
Showing the changes to Documentation/core-api (1 of 3 files). Show all
Unified · Split
| @@ -132,6 +132,7 @@ Some additional variants exist for more specialized cases: · 131 unmodified lines | |||
| 132 | .. c:function:: u64 ktime_get_mono_fast_ns( void ) | 132 | .. c:function:: u64 ktime_get_mono_fast_ns( void ) |
| 133 | u64 ktime_get_raw_fast_ns( void ) | 133 | u64 ktime_get_raw_fast_ns( void ) |
| 134 | u64 ktime_get_boot_fast_ns( void ) | 134 | u64 ktime_get_boot_fast_ns( void ) |
| 135 | u64 ktime_get_tai_fast_ns( void ) | ||
| 135 | u64 ktime_get_real_fast_ns( void ) | 136 | u64 ktime_get_real_fast_ns( void ) |
| 136 | 137 | ||
| 137 | These variants are safe to call from any context, including from | 138 | These variants are safe to call from any context, including from |