Lines Matching refs:ClockSnapshot

10 trace time, as long as the [ClockSnapshot][clock_snapshot] packets are present in
39 2. [The ClockSnapshot trace packet](#clock_snapshot)
48   // one of the built-in types from ClockSnapshot::BuiltinClocks, or a
89 * Emit at least once a [`ClockSnapshot`][clock_snapshot] packet.
91 Such `ClockSnapshot`:
111 The same `ClockSnapshot` rules as above apply. The only difference is that once
112 a `ClockSnapshot` defines a clock domain with ID >= 128, that clock domain can
126 ### {#clock_snapshot} The ClockSnapshot trace packet
128 The [`ClockSnapshot`][clock_snapshot] packet defines sync points between two or
136 The `traced` service automatically emits `ClockSnapshot` packets for the builtin
139 A data source should emit `ClockSnapshot` packets only when using custom clock
142 It is *not* mandatory that the `ClockSnapshot` for a custom clock domain
151 `ClockSnapshot` packets seen until then using nearest neighbor approximation.
153 For instance, assume that the trace contains `ClockSnapshot` for
177 `ClockSnapshot` packets.
182 In this sense `ClockSnapshot` packets define edges of an acyclic graph that is
224 `ClockSnapshot` packets).