2 RFC: Common Trace Format (CTF) Proposal (pre-v1.7)
4 Mathieu Desnoyers, EfficiOS Inc.
6 The goal of the present document is to propose a trace format that suits the
7 needs of the embedded, telecom, high-performance and kernel communities. It is
8 based on the Common Trace Format Requirements (v1.4) document. It is designed to
9 allow traces to be natively generated by the Linux kernel, Linux user-space
10 applications written in C/C++, and hardware components. One major element of
11 CTF is the Trace Stream Description Language (TSDL) which flexibility
12 enables description of various binary trace stream layouts.
14 The latest version of this document can be found at:
16 git tree: git://git.efficios.com/ctf.git
17 gitweb: http://git.efficios.com/?p=ctf.git
19 A reference implementation of a library to read and write this trace format is
20 being implemented within the BabelTrace project, a converter between trace
21 formats. The development tree is available at:
23 git tree: git://git.efficios.com/babeltrace.git
24 gitweb: http://git.efficios.com/?p=babeltrace.git
27 1. Preliminary definitions
29 - Event Trace: An ordered sequence of events.
30 - Event Stream: An ordered sequence of events, containing a subset of the
32 - Event Packet: A sequence of physically contiguous events within an event
34 - Event: This is the basic entry in a trace. (aka: a trace record).
35 - An event identifier (ID) relates to the class (a type) of event within
37 e.g. event: irq_entry.
38 - An event (or event record) relates to a specific instance of an event
40 e.g. event: irq_entry, at time X, on CPU Y
41 - Source Architecture: Architecture writing the trace.
42 - Reader Architecture: Architecture reading the trace.
45 2. High-level representation of a trace
47 A trace is divided into multiple event streams. Each event stream contains a
48 subset of the trace event types.
50 The final output of the trace, after its generation and optional transport over
51 the network, is expected to be either on permanent or temporary storage in a
52 virtual file system. Because each event stream is appended to while a trace is
53 being recorded, each is associated with a separate file for output. Therefore,
54 a stored trace can be represented as a directory containing one file per stream.
56 Meta-data description associated with the trace contains information on
57 trace event types expressed in the Trace Stream Description Language
58 (TSDL). This language describes:
62 - Per-trace event header description.
63 - Per-stream event header description.
64 - Per-stream event context description.
66 - Event type to stream mapping.
67 - Event type to name mapping.
68 - Event type to ID mapping.
69 - Event context description.
70 - Event fields description.
75 An event stream can be divided into contiguous event packets of variable
76 size. These subdivisions have a variable size. An event packet can
77 contain a certain amount of padding at the end. The stream header is
78 repeated at the beginning of each event packet. The rationale for the
79 event stream design choices is explained in Appendix B. Stream Header
82 The event stream header will therefore be referred to as the "event packet
83 header" throughout the rest of this document.
88 Types are organized as type classes. Each type class belong to either of two
89 kind of types: basic types or compound types.
93 A basic type is a scalar type, as described in this section. It includes
94 integers, GNU/C bitfields, enumerations, and floating point values.
96 4.1.1 Type inheritance
98 Type specifications can be inherited to allow deriving types from a
99 type class. For example, see the uint32_t named type derived from the "integer"
100 type class below ("Integers" section). Types have a precise binary
101 representation in the trace. A type class has methods to read and write these
102 types, but must be derived into a type to be usable in an event field.
106 We define "byte-packed" types as aligned on the byte size, namely 8-bit.
107 We define "bit-packed" types as following on the next bit, as defined by the
110 Each basic type must specify its alignment, in bits. Examples of
111 possible alignments are: bit-packed (align = 1), byte-packed (align =
112 8), or word-aligned (e.g. align = 32 or align = 64). The choice depends
113 on the architecture preference and compactness vs performance trade-offs
114 of the implementation. Architectures providing fast unaligned write
115 byte-packed basic types to save space, aligning each type on byte
116 boundaries (8-bit). Architectures with slow unaligned writes align types
117 on specific alignment values. If no specific alignment is declared for a
118 type, it is assumed to be bit-packed for integers with size not multiple
119 of 8 bits and for gcc bitfields. All other basic types are byte-packed
120 by default. It is however recommended to always specify the alignment
121 explicitly. Alignment values must be power of two. Compound types are
122 aligned as specified in their individual specification.
124 TSDL meta-data attribute representation of a specific alignment:
126 align = value; /* value in bits */
130 By default, the native endianness of the source architecture the trace is used.
131 Byte order can be overridden for a basic type by specifying a "byte_order"
132 attribute. Typical use-case is to specify the network byte order (big endian:
133 "be") to save data captured from the network into the trace without conversion.
134 If not specified, the byte order is native.
136 TSDL meta-data representation:
138 byte_order = native OR network OR be OR le; /* network and be are aliases */
142 Type size, in bits, for integers and floats is that returned by "sizeof()" in C
143 multiplied by CHAR_BIT.
144 We require the size of "char" and "unsigned char" types (CHAR_BIT) to be fixed
145 to 8 bits for cross-endianness compatibility.
147 TSDL meta-data representation:
149 size = value; (value is in bits)
153 Signed integers are represented in two-complement. Integer alignment,
154 size, signedness and byte ordering are defined in the TSDL meta-data.
155 Integers aligned on byte size (8-bit) and with length multiple of byte
156 size (8-bit) correspond to the C99 standard integers. In addition,
157 integers with alignment and/or size that are _not_ a multiple of the
158 byte size are permitted; these correspond to the C99 standard bitfields,
159 with the added specification that the CTF integer bitfields have a fixed
160 binary representation. A MIT-licensed reference implementation of the
161 CTF portable bitfields is available at:
163 http://git.efficios.com/?p=babeltrace.git;a=blob;f=include/babeltrace/bitfield.h
165 Binary representation of integers:
167 - On little and big endian:
168 - Within a byte, high bits correspond to an integer high bits, and low bits
169 correspond to low bits.
171 - Integer across multiple bytes are placed from the less significant to the
173 - Consecutive integers are placed from lower bits to higher bits (even within
176 - Integer across multiple bytes are placed from the most significant to the
178 - Consecutive integers are placed from higher bits to lower bits (even within
181 This binary representation is derived from the bitfield implementation in GCC
182 for little and big endian. However, contrary to what GCC does, integers can
183 cross units boundaries (no padding is required). Padding can be explicitly
184 added (see 4.1.6 GNU/C bitfields) to follow the GCC layout if needed.
186 TSDL meta-data representation:
189 signed = true OR false; /* default false */
190 byte_order = native OR network OR be OR le; /* default native */
191 size = value; /* value in bits, no default */
192 align = value; /* value in bits */
193 /* based used for pretty-printing output, default: decimal. */
194 base = decimal OR dec OR OR d OR i OR u OR 10 OR hexadecimal OR hex OR x OR X OR p OR 16
195 OR octal OR oct OR o OR 8 OR binary OR b OR 2;
198 Example of type inheritance (creation of a uint32_t named type):
206 Definition of a named 5-bit signed bitfield:
214 4.1.6 GNU/C bitfields
216 The GNU/C bitfields follow closely the integer representation, with a
217 particularity on alignment: if a bitfield cannot fit in the current unit, the
218 unit is padded and the bitfield starts at the following unit. The unit size is
219 defined by the size of the type "unit_type".
221 TSDL meta-data representation:
225 As an example, the following structure declared in C compiled by GCC:
232 The example structure is aligned on the largest element (short). The second
233 bitfield would be aligned on the next unit boundary, because it would not fit in
238 The floating point values byte ordering is defined in the TSDL meta-data.
240 Floating point values follow the IEEE 754-2008 standard interchange formats.
241 Description of the floating point values include the exponent and mantissa size
242 in bits. Some requirements are imposed on the floating point values:
244 - FLT_RADIX must be 2.
245 - mant_dig is the number of digits represented in the mantissa. It is specified
246 by the ISO C99 standard, section 5.2.4, as FLT_MANT_DIG, DBL_MANT_DIG and
247 LDBL_MANT_DIG as defined by <float.h>.
248 - exp_dig is the number of digits represented in the exponent. Given that
249 mant_dig is one bit more than its actual size in bits (leading 1 is not
250 needed) and also given that the sign bit always takes one bit, exp_dig can be
253 - sizeof(float) * CHAR_BIT - FLT_MANT_DIG
254 - sizeof(double) * CHAR_BIT - DBL_MANT_DIG
255 - sizeof(long double) * CHAR_BIT - LDBL_MANT_DIG
257 TSDL meta-data representation:
262 byte_order = native OR network OR be OR le;
266 Example of type inheritance:
268 typealias floating_point {
269 exp_dig = 8; /* sizeof(float) * CHAR_BIT - FLT_MANT_DIG */
270 mant_dig = 24; /* FLT_MANT_DIG */
275 TODO: define NaN, +inf, -inf behavior.
277 Bit-packed, byte-packed or larger alignments can be used for floating
278 point values, similarly to integers.
282 Enumerations are a mapping between an integer type and a table of strings. The
283 numerical representation of the enumeration follows the integer type specified
284 by the meta-data. The enumeration mapping table is detailed in the enumeration
285 description within the meta-data. The mapping table maps inclusive value
286 ranges (or single values) to strings. Instead of being limited to simple
287 "value -> string" mappings, these enumerations map
288 "[ start_value ... end_value ] -> string", which map inclusive ranges of
289 values to strings. An enumeration from the C language can be represented in
290 this format by having the same start_value and end_value for each element, which
291 is in fact a range of size 1. This single-value range is supported without
292 repeating the start and end values with the value = string declaration.
294 enum name : integer_type {
295 somestring = start_value1 ... end_value1,
296 "other string" = start_value2 ... end_value2,
297 yet_another_string, /* will be assigned to end_value2 + 1 */
298 "some other string" = value,
302 If the values are omitted, the enumeration starts at 0 and increment of 1 for
305 enum name : unsigned int {
313 Overlapping ranges within a single enumeration are implementation defined.
315 A nameless enumeration can be declared as a field type or as part of a typedef:
317 enum : integer_type {
321 Enumerations omitting the container type ": integer_type" use the "int"
322 type (for compatibility with C99). The "int" type must be previously
325 typealias integer { size = 32; align = 32; signed = true } := int;
334 Compound are aggregation of type declarations. Compound types include
335 structures, variant, arrays, sequences, and strings.
339 Structures are aligned on the largest alignment required by basic types
340 contained within the structure. (This follows the ISO/C standard for structures)
342 TSDL meta-data representation of a named structure:
345 field_type field_name;
346 field_type field_name;
353 integer { /* Nameless type */
358 uint64_t second_field_name; /* Named type declared in the meta-data */
361 The fields are placed in a sequence next to each other. They each possess a
362 field name, which is a unique identifier within the structure.
364 A nameless structure can be declared as a field type or as part of a typedef:
370 Alignment for a structure compound type can be forced to a minimum value
371 by adding an "align" specifier after the declaration of a structure
372 body. This attribute is read as: align(value). The value is specified in
373 bits. The structure will be aligned on the maximum value between this
374 attribute and the alignment required by the basic types contained within
381 4.2.2 Variants (Discriminated/Tagged Unions)
383 A CTF variant is a selection between different types. A CTF variant must
384 always be defined within the scope of a structure or within fields
385 contained within a structure (defined recursively). A "tag" enumeration
386 field must appear in either the same lexical scope, prior to the variant
387 field (in field declaration order), in an uppermost lexical scope (see
388 Section 7.3.1), or in an uppermost dynamic scope (see Section 7.3.2).
389 The type selection is indicated by the mapping from the enumeration
390 value to the string used as variant type selector. The field to use as
391 tag is specified by the "tag_field", specified between "< >" after the
392 "variant" keyword for unnamed variants, and after "variant name" for
395 The alignment of the variant is the alignment of the type as selected by the tag
396 value for the specific instance of the variant. The alignment of the type
397 containing the variant is independent of the variant alignment. The size of the
398 variant is the size as selected by the tag value for the specific instance of
401 A named variant declaration followed by its definition within a structure
412 enum : integer_type { sel1, sel2, sel3, ... } tag_field;
414 variant name <tag_field> v;
417 An unnamed variant definition within a structure is expressed by the following
421 enum : integer_type { sel1, sel2, sel3, ... } tag_field;
423 variant <tag_field> {
431 Example of a named variant within a sequence that refers to a single tag field:
440 enum : uint2_t { a, b, c } choice;
441 variant example <choice> v[unsigned int];
444 Example of an unnamed variant:
447 enum : uint2_t { a, b, c, d } choice;
448 /* Unrelated fields can be added between the variant and its tag */
461 Example of an unnamed variant within an array:
464 enum : uint2_t { a, b, c } choice;
472 Example of a variant type definition within a structure, where the defined type
473 is then declared within an array of structures. This variant refers to a tag
474 located in an upper lexical scope. This example clearly shows that a variant
475 type definition referring to the tag "x" uses the closest preceding field from
476 the lexical scope of the type definition.
479 enum : uint2_t { a, b, c, d } x;
481 typedef variant <x> { /*
482 * "x" refers to the preceding "x" enumeration in the
483 * lexical scope of the type definition.
491 enum : int { x, y, z } x; /* This enumeration is not used by "v". */
492 example_variant v; /*
493 * "v" uses the "enum : uint2_t { a, b, c, d }"
501 Arrays are fixed-length. Their length is declared in the type
502 declaration within the meta-data. They contain an array of "inner type"
503 elements, which can refer to any type not containing the type of the
504 array being declared (no circular dependency). The length is the number
505 of elements in an array.
507 TSDL meta-data representation of a named array:
509 typedef elem_type name[length];
511 A nameless array can be declared as a field type within a structure, e.g.:
513 uint8_t field_name[10];
515 Arrays are always aligned on their element alignment requirement.
519 Sequences are dynamically-sized arrays. They start with an integer that specify
520 the length of the sequence, followed by an array of "inner type" elements.
521 The length is the number of elements in the sequence.
523 TSDL meta-data representation for a named sequence:
525 typedef elem_type name[length_type];
527 A nameless sequence can be declared as a field type, e.g.:
529 long field_name[int];
531 The length type follows the integer types specifications, and the sequence
532 elements follow the "array" specifications.
536 Strings are an array of bytes of variable size and are terminated by a '\0'
537 "NULL" character. Their encoding is described in the TSDL meta-data. In
538 absence of encoding attribute information, the default encoding is
541 TSDL meta-data representation of a named string type:
544 encoding = UTF8 OR ASCII;
547 A nameless string type can be declared as a field type:
549 string field_name; /* Use default UTF8 encoding */
551 Strings are always aligned on byte size.
553 5. Event Packet Header
555 The event packet header consists of two parts: the "event packet header"
556 is the same for all streams of a trace. The second part, the "event
557 packet context", is described on a per-stream basis. Both are described
558 in the TSDL meta-data. The packets are aligned on architecture-page-sized
561 Event packet header (all fields are optional, specified by TSDL meta-data):
563 - Magic number (CTF magic number: 0xC1FC1FC1) specifies that this is a
564 CTF packet. This magic number is optional, but when present, it should
565 come at the very beginning of the packet.
566 - Trace UUID, used to ensure the event packet match the meta-data used.
567 (note: we cannot use a meta-data checksum in every cases instead of a
568 UUID because meta-data can be appended to while tracing is active)
569 This field is optional.
570 - Stream ID, used as reference to stream description in meta-data.
571 This field is optional if there is only one stream description in the
572 meta-data, but becomes required if there are more than one stream in
573 the TSDL meta-data description.
575 Event packet context (all fields are optional, specified by TSDL meta-data):
577 - Event packet content size (in bytes).
578 - Event packet size (in bytes, includes padding).
579 - Event packet content checksum (optional). Checksum excludes the event packet
581 - Per-stream event packet sequence count (to deal with UDP packet loss). The
582 number of significant sequence counter bits should also be present, so
583 wrap-arounds are dealt with correctly.
584 - Time-stamp at the beginning and time-stamp at the end of the event packet.
585 Both timestamps are written in the packet header, but sampled respectively
586 while (or before) writing the first event and while (or after) writing the
587 last event in the packet. The inclusive range between these timestamps should
588 include all event timestamps assigned to events contained within the packet.
589 - Events discarded count
590 - Snapshot of a per-stream free-running counter, counting the number of
591 events discarded that were supposed to be written in the stream prior to
592 the first event in the event packet.
593 * Note: producer-consumer buffer full condition should fill the current
594 event packet with padding so we know exactly where events have been
596 - Lossless compression scheme used for the event packet content. Applied
597 directly to raw data. New types of compression can be added in following
598 versions of the format.
599 0: no compression scheme
603 - Cypher used for the event packet content. Applied after compression.
606 - Checksum scheme used for the event packet content. Applied after encryption.
612 5.1 Event Packet Header Description
614 The event packet header layout is indicated by the trace packet.header
615 field. Here is a recommended structure type for the packet header with
616 the fields typically expected (although these fields are each optional):
618 struct event_packet_header {
620 uint8_t trace_uuid[16];
626 packet.header := struct event_packet_header;
629 If the magic number is not present, tools such as "file" will have no
630 mean to discover the file type.
632 If the trace_uuid is not present, no validation that the meta-data
633 actually corresponds to the stream is performed.
635 If the stream_id packet header field is missing, the trace can only
636 contain a single stream. Its "id" field can be left out, and its events
637 don't need to declare a "stream_id" field.
640 5.2 Event Packet Context Description
642 Event packet context example. These are declared within the stream declaration
643 in the meta-data. All these fields are optional. If the packet size field is
644 missing, the whole stream only contains a single packet. If the content
645 size field is missing, the packet is filled (no padding). The content
646 and packet sizes include all headers.
648 An example event packet context type:
650 struct event_packet_context {
651 uint64_t timestamp_begin;
652 uint64_t timestamp_end;
654 uint32_t stream_packet_count;
655 uint32_t events_discarded;
657 uint32_t/uint16_t content_size;
658 uint32_t/uint16_t packet_size;
659 uint8_t stream_packet_count_bits; /* Significant counter bits */
660 uint8_t compression_scheme;
661 uint8_t encryption_scheme;
662 uint8_t checksum_scheme;
668 The overall structure of an event is:
670 1 - Stream Packet Context (as specified by the stream meta-data)
671 2 - Event Header (as specified by the stream meta-data)
672 3 - Stream Event Context (as specified by the stream meta-data)
673 4 - Event Context (as specified by the event meta-data)
674 5 - Event Payload (as specified by the event meta-data)
676 This structure defines an implicit dynamic scoping, where variants
677 located in inner structures (those with a higher number in the listing
678 above) can refer to the fields of outer structures (with lower number in
679 the listing above). See Section 7.3 TSDL Scopes for more detail.
683 Event headers can be described within the meta-data. We hereby propose, as an
684 example, two types of events headers. Type 1 accommodates streams with less than
685 31 event IDs. Type 2 accommodates streams with 31 or more event IDs.
687 One major factor can vary between streams: the number of event IDs assigned to
688 a stream. Luckily, this information tends to stay relatively constant (modulo
689 event registration while trace is being recorded), so we can specify different
690 representations for streams containing few event IDs and streams containing
691 many event IDs, so we end up representing the event ID and time-stamp as
692 densely as possible in each case.
694 The header is extended in the rare occasions where the information cannot be
695 represented in the ranges available in the standard event header. They are also
696 used in the rare occasions where the data required for a field could not be
697 collected: the flag corresponding to the missing field within the missing_fields
698 array is then set to 1.
700 Types uintX_t represent an X-bit unsigned integer, as declared with
703 typealias integer { size = X; align = X; signed = false } := uintX_t;
707 typealias integer { size = X; align = 1; signed = false } := uintX_t;
709 6.1.1 Type 1 - Few event IDs
711 - Aligned on 32-bit (or 8-bit if byte-packed, depending on the architecture
713 - Native architecture byte ordering.
714 - For "compact" selection
715 - Fixed size: 32 bits.
716 - For "extended" selection
717 - Size depends on the architecture and variant alignment.
719 struct event_header_1 {
722 * id 31 is reserved to indicate an extended header.
724 enum : uint5_t { compact = 0 ... 30, extended = 31 } id;
730 uint32_t id; /* 32-bit event IDs */
731 uint64_t timestamp; /* 64-bit timestamps */
737 6.1.2 Type 2 - Many event IDs
739 - Aligned on 16-bit (or 8-bit if byte-packed, depending on the architecture
741 - Native architecture byte ordering.
742 - For "compact" selection
743 - Size depends on the architecture and variant alignment.
744 - For "extended" selection
745 - Size depends on the architecture and variant alignment.
747 struct event_header_2 {
749 * id: range: 0 - 65534.
750 * id 65535 is reserved to indicate an extended header.
752 enum : uint16_t { compact = 0 ... 65534, extended = 65535 } id;
758 uint32_t id; /* 32-bit event IDs */
759 uint64_t timestamp; /* 64-bit timestamps */
767 The event context contains information relative to the current event.
768 The choice and meaning of this information is specified by the TSDL
769 stream and event meta-data descriptions. The stream context is applied
770 to all events within the stream. The stream context structure follows
771 the event header. The event context is applied to specific events. Its
772 structure follows the stream context structure.
774 An example of stream-level event context is to save the event payload size with
775 each event, or to save the current PID with each event. These are declared
776 within the stream declaration within the meta-data:
780 event.context := struct {
782 uint16_t payload_size;
786 An example of event-specific event context is to declare a bitmap of missing
787 fields, only appended after the stream event context if the extended event
788 header is selected. NR_FIELDS is the number of fields within the event (a
796 uint1_t missing_fields[NR_FIELDS]; /* missing event fields bitmap */
805 An event payload contains fields specific to a given event type. The fields
806 belonging to an event type are described in the event-specific meta-data
807 within a structure type.
811 No padding at the end of the event payload. This differs from the ISO/C standard
812 for structures, but follows the CTF standard for structures. In a trace, even
813 though it makes sense to align the beginning of a structure, it really makes no
814 sense to add padding at the end of the structure, because structures are usually
815 not followed by a structure of the same type.
817 This trick can be done by adding a zero-length "end" field at the end of the C
818 structures, and by using the offset of this field rather than using sizeof()
819 when calculating the size of a structure (see Appendix "A. Helper macros").
823 The event payload is aligned on the largest alignment required by types
824 contained within the payload. (This follows the ISO/C standard for structures)
827 7. Trace Stream Description Language (TSDL)
829 The Trace Stream Description Language (TSDL) allows expression of the
830 binary trace streams layout in a C99-like Domain Specific Language
836 The trace stream layout description is located in the trace meta-data.
837 The meta-data is itself located in a stream identified by its name:
840 The meta-data description can be expressed in two different formats:
841 text-only and packet-based. The text-only description facilitates
842 generation of meta-data and provides a convenient way to enter the
843 meta-data information by hand. The packet-based meta-data provides the
844 CTF stream packet facilities (checksumming, compression, encryption,
845 network-readiness) for meta-data stream generated and transported by a
848 The text-only meta-data file is a plain text TSDL description.
850 The packet-based meta-data is made of "meta-data packets", which each
851 start with a meta-data packet header. The packet-based meta-data
852 description is detected by reading the magic number "0x75D11D57" at the
853 beginning of the file. This magic number is also used to detect the
854 endianness of the architecture by trying to read the CTF magic number
855 and its counterpart in reversed endianness. The events within the
856 meta-data stream have no event header nor event context. Each event only
857 contains a "string" payload. Each meta-data packet start with a special
858 packet header, specific to the meta-data stream, which contains,
861 struct metadata_packet_header {
862 uint32_t magic; /* 0x75D11D57 */
863 uint8_t trace_uuid[16]; /* Unique Universal Identifier */
864 uint32_t checksum; /* 0 if unused */
865 uint32_t content_size; /* in bits */
866 uint32_t packet_size; /* in bits */
867 uint8_t compression_scheme; /* 0 if unused */
868 uint8_t encryption_scheme; /* 0 if unused */
869 uint8_t checksum_scheme; /* 0 if unused */
872 The packet-based meta-data can be converted to a text-only meta-data by
873 concatenating all the strings in contains.
875 In the textual representation of the meta-data, the text contained
876 within "/*" and "*/", as well as within "//" and end of line, are
877 treated as comments. Boolean values can be represented as true, TRUE,
878 or 1 for true, and false, FALSE, or 0 for false. Within the string-based
879 meta-data description, the trace UUID is represented as a string of
880 hexadecimal digits and dashes "-". In the event packet header, the trace
881 UUID is represented as an array of bytes.
884 7.2 Declaration vs Definition
886 A declaration associates a layout to a type, without specifying where
887 this type is located in the event structure hierarchy (see Section 6).
888 This therefore includes typedef, typealias, as well as all type
889 specifiers. In certain circumstances (typedef, structure field and
890 variant field), a declaration is followed by a declarator, which specify
891 the newly defined type name (for typedef), or the field name (for
892 declarations located within structure and variants). Array and sequence,
893 declared with square brackets ("[" "]"), are part of the declarator,
894 similarly to C99. The enumeration base type is specified by
895 ": enum_base", which is part of the type specifier. The variant tag
896 name, specified between "<" ">", is also part of the type specifier.
898 A definition associates a type to a location in the event structure
899 hierarchy (see Section 6). This association is denoted by ":=", as shown
905 TSDL uses two different types of scoping: a lexical scope is used for
906 declarations and type definitions, and a dynamic scope is used for
907 variants references to tag fields.
911 Each of "trace", "stream", "event", "struct" and "variant" have their own
912 nestable declaration scope, within which types can be declared using "typedef"
913 and "typealias". A root declaration scope also contains all declarations
914 located outside of any of the aforementioned declarations. An inner
915 declaration scope can refer to type declared within its container
916 lexical scope prior to the inner declaration scope. Redefinition of a
917 typedef or typealias is not valid, although hiding an upper scope
918 typedef or typealias is allowed within a sub-scope.
922 A dynamic scope consists in the lexical scope augmented with the
923 implicit event structure definition hierarchy presented at Section 6.
924 The dynamic scope is only used for variant tag definitions. It is used
925 at definition time to look up the location of the tag field associated
928 Therefore, variants in lower levels in the dynamic scope (e.g. event
929 context) can refer to a tag field located in upper levels (e.g. in the
930 event header) by specifying, in this case, the associated tag with
931 <header.field_name>. This allows, for instance, the event context to
932 define a variant referring to the "id" field of the event header as
935 The target dynamic scope must be specified explicitly when referring to
936 a field outside of the local static scope. The dynamic scope prefixes
939 - Trace Packet Header: <trace.packet.header. >,
940 - Stream Packet Context: <stream.packet.context. >,
941 - Event Header: <stream.event.header. >,
942 - Stream Event Context: <stream.event.context. >,
943 - Event Context: <event.context. >,
944 - Event Payload: <event.fields. >.
946 Multiple declarations of the same field name within a single scope is
947 not valid. It is however valid to re-use the same field name in
948 different scopes. There is no possible conflict, because the dynamic
949 scope must be specified when a variant refers to a tag field located in
950 a different dynamic scope.
952 The information available in the dynamic scopes can be thought of as the
953 current tracing context. At trace production, information about the
954 current context is saved into the specified scope field levels. At trace
955 consumption, for each event, the current trace context is therefore
956 readable by accessing the upper dynamic scopes.
961 The grammar representing the TSDL meta-data is presented in Appendix C.
962 TSDL Grammar. This section presents a rather lighter reading that
963 consists in examples of TSDL meta-data, with template values.
965 The stream "id" can be left out if there is only one stream in the
966 trace. The event "id" field can be left out if there is only one event
970 major = value; /* Trace format version */
972 uuid = "aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa"; /* Trace UUID */
973 byte_order = be OR le; /* Endianness (required) */
974 packet.header := struct {
976 uint8_t trace_uuid[16];
983 /* Type 1 - Few event IDs; Type 2 - Many event IDs. See section 6.1. */
984 event.header := event_header_1 OR event_header_2;
985 event.context := struct {
988 packet.context := struct {
995 id = value; /* Numeric identifier within the stream */
996 stream_id = stream_id;
1005 /* More detail on types in section 4. Types */
1010 * Type declarations behave similarly to the C standard.
1013 typedef aliased_type_specifiers new_type_declarators;
1015 /* e.g.: typedef struct example new_type_name[10]; */
1020 * The "typealias" declaration can be used to give a name (including
1021 * pointer declarator specifier) to a type. It should also be used to
1022 * map basic C types (float, int, unsigned long, ...) to a CTF type.
1023 * Typealias is a superset of "typedef": it also allows assignment of a
1024 * simple variable identifier to a type.
1027 typealias type_class {
1029 } := type_specifiers type_declarator;
1033 * typealias integer {
1037 * } := struct page *;
1039 * typealias integer {
1054 enum name : integer_type {
1060 * Unnamed types, contained within compound type fields, typedef or typealias.
1075 enum : integer_type {
1079 typedef type new_type[length];
1082 type field_name[length];
1085 typedef type new_type[length_type];
1088 type field_name[length_type];
1100 integer_type field_name:size; /* GNU/C bitfield */
1110 The two following macros keep track of the size of a GNU/C structure without
1111 padding at the end by placing HEADER_END as the last field. A one byte end field
1112 is used for C90 compatibility (C99 flexible arrays could be used here). Note
1113 that this does not affect the effective structure size, which should always be
1114 calculated with the header_sizeof() helper.
1116 #define HEADER_END char end_field
1117 #define header_sizeof(type) offsetof(typeof(type), end_field)
1120 B. Stream Header Rationale
1122 An event stream is divided in contiguous event packets of variable size. These
1123 subdivisions allow the trace analyzer to perform a fast binary search by time
1124 within the stream (typically requiring to index only the event packet headers)
1125 without reading the whole stream. These subdivisions have a variable size to
1126 eliminate the need to transfer the event packet padding when partially filled
1127 event packets must be sent when streaming a trace for live viewing/analysis.
1128 An event packet can contain a certain amount of padding at the end. Dividing
1129 streams into event packets is also useful for network streaming over UDP and
1130 flight recorder mode tracing (a whole event packet can be swapped out of the
1131 buffer atomically for reading).
1133 The stream header is repeated at the beginning of each event packet to allow
1134 flexibility in terms of:
1136 - streaming support,
1137 - allowing arbitrary buffers to be discarded without making the trace
1139 - allow UDP packet loss handling by either dealing with missing event packet
1140 or asking for re-transmission.
1141 - transparently support flight recorder mode,
1142 - transparently support crash dump.
1148 * Common Trace Format (CTF) Trace Stream Description Language (TSDL) Grammar.
1150 * Inspired from the C99 grammar:
1151 * http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1124.pdf (Annex A)
1152 * and c++1x grammar (draft)
1153 * http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2011/n3291.pdf (Annex A)
1155 * Specialized for CTF needs by including only constant and declarations from
1156 * C99 (excluding function declarations), and by adding support for variants,
1157 * sequences and CTF-specific specifiers. Enumeration container types
1158 * semantic is inspired from c++1x enum-base.
1163 1.1) Lexical elements
1207 identifier identifier-nondigit
1210 identifier-nondigit:
1212 universal-character-name
1213 any other implementation-defined characters
1217 [a-zA-Z] /* regular expression */
1220 [0-9] /* regular expression */
1222 1.4) Universal character names
1224 universal-character-name:
1226 \U hex-quad hex-quad
1229 hexadecimal-digit hexadecimal-digit hexadecimal-digit hexadecimal-digit
1235 enumeration-constant
1239 decimal-constant integer-suffix-opt
1240 octal-constant integer-suffix-opt
1241 hexadecimal-constant integer-suffix-opt
1245 decimal-constant digit
1249 octal-constant octal-digit
1251 hexadecimal-constant:
1252 hexadecimal-prefix hexadecimal-digit
1253 hexadecimal-constant hexadecimal-digit
1263 unsigned-suffix long-suffix-opt
1264 unsigned-suffix long-long-suffix
1265 long-suffix unsigned-suffix-opt
1266 long-long-suffix unsigned-suffix-opt
1280 enumeration-constant:
1286 L' c-char-sequence '
1290 c-char-sequence c-char
1293 any member of source charset except single-quote ('), backslash
1294 (\), or new-line character.
1298 simple-escape-sequence
1299 octal-escape-sequence
1300 hexadecimal-escape-sequence
1301 universal-character-name
1303 simple-escape-sequence: one of
1304 \' \" \? \\ \a \b \f \n \r \t \v
1306 octal-escape-sequence:
1308 \ octal-digit octal-digit
1309 \ octal-digit octal-digit octal-digit
1311 hexadecimal-escape-sequence:
1312 \x hexadecimal-digit
1313 hexadecimal-escape-sequence hexadecimal-digit
1315 1.6) String literals
1318 " s-char-sequence-opt "
1319 L" s-char-sequence-opt "
1323 s-char-sequence s-char
1326 any member of source charset except double-quote ("), backslash
1327 (\), or new-line character.
1333 [ ] ( ) { } . -> * + - < > : ; ... = ,
1336 2) Phrase structure grammar
1342 ( unary-expression )
1346 postfix-expression [ unary-expression ]
1347 postfix-expression . identifier
1348 postfix-expressoin -> identifier
1352 unary-operator postfix-expression
1354 unary-operator: one of
1357 assignment-operator:
1360 type-assignment-operator:
1363 constant-expression:
1366 constant-expression-range:
1367 constant-expression ... constant-expression
1372 declaration-specifiers declarator-list-opt ;
1375 declaration-specifiers:
1376 storage-class-specifier declaration-specifiers-opt
1377 type-specifier declaration-specifiers-opt
1378 type-qualifier declaration-specifiers-opt
1382 declarator-list , declarator
1384 abstract-declarator-list:
1386 abstract-declarator-list , abstract-declarator
1388 storage-class-specifier:
1411 align ( constant-expression )
1414 struct identifier-opt { struct-or-variant-declaration-list-opt } align-attribute-opt
1415 struct identifier align-attribute-opt
1417 struct-or-variant-declaration-list:
1418 struct-or-variant-declaration
1419 struct-or-variant-declaration-list struct-or-variant-declaration
1421 struct-or-variant-declaration:
1422 specifier-qualifier-list struct-or-variant-declarator-list ;
1423 declaration-specifiers storage-class-specifier declaration-specifiers declarator-list ;
1424 typealias declaration-specifiers abstract-declarator-list := declaration-specifiers abstract-declarator-list ;
1425 typealias declaration-specifiers abstract-declarator-list := declarator-list ;
1427 specifier-qualifier-list:
1428 type-specifier specifier-qualifier-list-opt
1429 type-qualifier specifier-qualifier-list-opt
1431 struct-or-variant-declarator-list:
1432 struct-or-variant-declarator
1433 struct-or-variant-declarator-list , struct-or-variant-declarator
1435 struct-or-variant-declarator:
1437 declarator-opt : constant-expression
1440 variant identifier-opt variant-tag-opt { struct-or-variant-declaration-list }
1441 variant identifier variant-tag
1447 enum identifier-opt { enumerator-list }
1448 enum identifier-opt { enumerator-list , }
1450 enum identifier-opt : declaration-specifiers { enumerator-list }
1451 enum identifier-opt : declaration-specifiers { enumerator-list , }
1455 enumerator-list , enumerator
1458 enumeration-constant
1459 enumeration-constant = constant-expression
1460 enumeration-constant = constant-expression-range
1466 pointer-opt direct-declarator
1471 direct-declarator [ type-specifier ]
1472 direct-declarator [ constant-expression ]
1474 abstract-declarator:
1475 pointer-opt direct-abstract-declarator
1477 direct-abstract-declarator:
1479 ( abstract-declarator )
1480 direct-abstract-declarator [ type-specifier ]
1481 direct-abstract-declarator [ constant-expression ]
1482 direct-abstract-declarator [ ]
1485 * type-qualifier-list-opt
1486 * type-qualifier-list-opt pointer
1488 type-qualifier-list:
1490 type-qualifier-list type-qualifier
1495 2.3) CTF-specific declarations
1498 event { ctf-assignment-expression-list-opt }
1499 stream { ctf-assignment-expression-list-opt }
1500 trace { ctf-assignment-expression-list-opt }
1501 typealias declaration-specifiers abstract-declarator-list := declaration-specifiers abstract-declarator-list ;
1502 typealias declaration-specifiers abstract-declarator-list := declarator-list ;
1505 floating_point { ctf-assignment-expression-list-opt }
1506 integer { ctf-assignment-expression-list-opt }
1507 string { ctf-assignment-expression-list-opt }
1509 ctf-assignment-expression-list:
1510 ctf-assignment-expression
1511 ctf-assignment-expression-list ; ctf-assignment-expression
1513 ctf-assignment-expression:
1514 unary-expression assignment-operator unary-expression
1515 unary-expression type-assignment-operator type-specifier
1516 declaration-specifiers storage-class-specifier declaration-specifiers declarator-list
1517 typealias declaration-specifiers abstract-declarator-list := declaration-specifiers abstract-declarator-list
1518 typealias declaration-specifiers abstract-declarator-list := declarator-list