X-Git-Url: http://git.efficios.com/?p=ctf.git;a=blobdiff_plain;f=common-trace-format-specification.txt;h=4af2244ab37adfa5a513cff029811cbdcc48bcea;hp=46c1013890bcbf5a3d047ffa0c80d32b3db1a62f;hb=ddd045b0ac45dcefe02f9e9320814b3e4adfc015;hpb=b46cfbf6a7ee8e30bf7bbf84009ceedeac4e4bf3 diff --git a/common-trace-format-specification.txt b/common-trace-format-specification.txt index 46c1013..4af2244 100644 --- a/common-trace-format-specification.txt +++ b/common-trace-format-specification.txt @@ -41,12 +41,12 @@ Table of Contents 4.1.6 GNU/C bitfields 4.1.7 Floating point 4.1.8 Enumerations -4.2 Compound types - 4.2.1 Structures - 4.2.2 Variants (Discriminated/Tagged Unions) - 4.2.3 Arrays - 4.2.4 Sequences - 4.2.5 Strings + 4.2 Compound types + 4.2.1 Structures + 4.2.2 Variants (Discriminated/Tagged Unions) + 4.2.3 Arrays + 4.2.4 Sequences + 4.2.5 Strings 5. Event Packet Header 5.1 Event Packet Header Description 5.2 Event Packet Context Description @@ -717,7 +717,11 @@ 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. + The timestamp at the beginning of an event packet is guaranteed to be + below or equal the timestamp at the end of that event packet. + The timestamp at the end of an event packet is guaranteed to be below + or equal the timestamps at the end of any following packet within the + same stream. 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 @@ -812,6 +816,12 @@ located in inner structures (those with a higher number in the listing above) can refer to the fields of outer structures (with lower number in the listing above). See Section 7.3 TSDL Scopes for more detail. +The total length of an event is defined as the difference between the +end of its Event Payload and the end of the previous event's Event +Payload. Therefore, it includes the event header alignment padding, and +all its fields and their respective alignment padding. Events of length +0 are forbidden. + 6.1 Event Header Event headers can be described within the meta-data. We hereby propose, as an