From 2a0bae9ec1c7b488839280f285cbf16a8d8ab9c0 Mon Sep 17 00:00:00 2001 From: Mathieu Desnoyers Date: Fri, 31 May 2013 10:58:24 -0400 Subject: [PATCH] Add timestamp fwd ref to clock section And clarify clock text. Signed-off-by: Mathieu Desnoyers --- common-trace-format-specification.txt | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/common-trace-format-specification.txt b/common-trace-format-specification.txt index b40193f..5320944 100644 --- a/common-trace-format-specification.txt +++ b/common-trace-format-specification.txt @@ -717,6 +717,7 @@ Event packet context (all fields are optional, specified by TSDL meta-data): while (or before) writing the first event and while (or after) writing the last event in the packet. The inclusive range between these timestamps should include all event timestamps assigned to events contained within the packet. + See Section 8. Clocks for more detail. - Events discarded count - Snapshot of a per-stream free-running counter, counting the number of events discarded that were supposed to be written in the stream after @@ -839,6 +840,8 @@ either: typealias integer { size = X; align = 1; signed = false; } := uintX_t; +For more information about timestamp fields, see Section 8. Clocks. + 6.1.1 Type 1 - Few event IDs - Aligned on 32-bit (or 8-bit if byte-packed, depending on the architecture @@ -1377,10 +1380,11 @@ stream { }; For a N-bit integer type referring to a clock, if the integer overflows -compared to the N low order bits of the clock prior value, then it is -assumed that one, and only one, overflow occurred. It is therefore -important that events encoding time on a small number of bits happen -frequently enough to detect when more than one N-bit overflow occurs. +compared to the N low order bits of the clock prior value found in the +same stream, then it is assumed that one, and only one, overflow +occurred. It is therefore important that events encoding time on a small +number of bits happen frequently enough to detect when more than one +N-bit overflow occurs. In a packet context, clock field names ending with "_begin" and "_end" have a special meaning: this refers to the time-stamps at, respectively, -- 2.34.1