445fe7ac733715fbce56c0c2185969759ecdc7be
[ctf.git] / common-trace-format-proposal.txt
1
2 RFC: Common Trace Format (CTF) Proposal (pre-v1.7)
3
4 Mathieu Desnoyers, EfficiOS Inc.
5
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.
11
12 The latest version of this document can be found at:
13
14 git tree: git://git.efficios.com/ctf.git
15 gitweb: http://git.efficios.com/?p=ctf.git
16
17 A reference implementation of a library to read and write this trace format is
18 being implemented within the BabelTrace project, a converter between trace
19 formats. The development tree is available at:
20
21 git tree: git://git.efficios.com/babeltrace.git
22 gitweb: http://git.efficios.com/?p=babeltrace.git
23
24
25 1. Preliminary definitions
26
27 - Event Trace: An ordered sequence of events.
28 - Event Stream: An ordered sequence of events, containing a subset of the
29 trace event types.
30 - Event Packet: A sequence of physically contiguous events within an event
31 stream.
32 - Event: This is the basic entry in a trace. (aka: a trace record).
33 - An event identifier (ID) relates to the class (a type) of event within
34 an event stream.
35 e.g. event: irq_entry.
36 - An event (or event record) relates to a specific instance of an event
37 class.
38 e.g. event: irq_entry, at time X, on CPU Y
39 - Source Architecture: Architecture writing the trace.
40 - Reader Architecture: Architecture reading the trace.
41
42
43 2. High-level representation of a trace
44
45 A trace is divided into multiple event streams. Each event stream contains a
46 subset of the trace event types.
47
48 The final output of the trace, after its generation and optional transport over
49 the network, is expected to be either on permanent or temporary storage in a
50 virtual file system. Because each event stream is appended to while a trace is
51 being recorded, each is associated with a separate file for output. Therefore,
52 a stored trace can be represented as a directory containing one file per stream.
53
54 A metadata event stream contains information on trace event types. It describes:
55
56 - Trace version.
57 - Types available.
58 - Per-stream event header description.
59 - Per-stream event header selection.
60 - Per-stream event context fields.
61 - Per-event
62 - Event type to stream mapping.
63 - Event type to name mapping.
64 - Event type to ID mapping.
65 - Event fields description.
66
67
68 3. Event stream
69
70 An event stream is divided in contiguous event packets of variable size. These
71 subdivisions have a variable size. An event packet can contain a certain
72 amount of padding at the end. The stream header is repeated at the
73 beginning of each event packet. The rationale for the event stream
74 design choices is explained in Appendix B. Stream Header Rationale.
75
76 The event stream header will therefore be referred to as the "event packet
77 header" throughout the rest of this document.
78
79
80 4. Types
81
82 Types are organized as type classes. Each type class belong to either of two
83 kind of types: basic types or compound types.
84
85 4.1 Basic types
86
87 A basic type is a scalar type, as described in this section. It includes
88 integers, GNU/C bitfields, enumerations, and floating point values.
89
90 4.1.1 Type inheritance
91
92 Type specifications can be inherited to allow deriving types from a
93 type class. For example, see the uint32_t named type derived from the "integer"
94 type class below ("Integers" section). Types have a precise binary
95 representation in the trace. A type class has methods to read and write these
96 types, but must be derived into a type to be usable in an event field.
97
98 4.1.2 Alignment
99
100 We define "byte-packed" types as aligned on the byte size, namely 8-bit.
101 We define "bit-packed" types as following on the next bit, as defined by the
102 "bitfields" section.
103
104 All basic types, except bitfields, are either aligned on an architecture-defined
105 specific alignment or byte-packed, depending on the architecture preference.
106 Architectures providing fast unaligned write byte-packed basic types to save
107 space, aligning each type on byte boundaries (8-bit). Architectures with slow
108 unaligned writes align types on specific alignment values. If no specific
109 alignment is declared for a type nor its parents, it is assumed to be bit-packed
110 for bitfields and byte-packed for other types.
111
112 Metadata attribute representation of a specific alignment:
113
114 align = value; /* value in bits */
115
116 4.1.3 Byte order
117
118 By default, the native endianness of the source architecture the trace is used.
119 Byte order can be overridden for a basic type by specifying a "byte_order"
120 attribute. Typical use-case is to specify the network byte order (big endian:
121 "be") to save data captured from the network into the trace without conversion.
122 If not specified, the byte order is native.
123
124 Metadata representation:
125
126 byte_order = native OR network OR be OR le; /* network and be are aliases */
127
128 4.1.4 Size
129
130 Type size, in bits, for integers and floats is that returned by "sizeof()" in C
131 multiplied by CHAR_BIT.
132 We require the size of "char" and "unsigned char" types (CHAR_BIT) to be fixed
133 to 8 bits for cross-endianness compatibility.
134
135 Metadata representation:
136
137 size = value; (value is in bits)
138
139 4.1.5 Integers
140
141 Signed integers are represented in two-complement. Integer alignment, size,
142 signedness and byte ordering are defined in the metadata. Integers aligned on
143 byte size (8-bit) and with length multiple of byte size (8-bit) correspond to
144 the C99 standard integers. In addition, integers with alignment and/or size that
145 are _not_ a multiple of the byte size are permitted; these correspond to the C99
146 standard bitfields, with the added specification that the CTF integer bitfields
147 have a fixed binary representation. A MIT-licensed reference implementation of
148 the CTF portable bitfields is available at:
149
150 http://git.efficios.com/?p=babeltrace.git;a=blob;f=include/babeltrace/bitfield.h
151
152 Binary representation of integers:
153
154 - On little and big endian:
155 - Within a byte, high bits correspond to an integer high bits, and low bits
156 correspond to low bits.
157 - On little endian:
158 - Integer across multiple bytes are placed from the less significant to the
159 most significant.
160 - Consecutive integers are placed from lower bits to higher bits (even within
161 a byte).
162 - On big endian:
163 - Integer across multiple bytes are placed from the most significant to the
164 less significant.
165 - Consecutive integers are placed from higher bits to lower bits (even within
166 a byte).
167
168 This binary representation is derived from the bitfield implementation in GCC
169 for little and big endian. However, contrary to what GCC does, integers can
170 cross units boundaries (no padding is required). Padding can be explicitely
171 added (see 4.1.6 GNU/C bitfields) to follow the GCC layout if needed.
172
173 Metadata representation:
174
175 integer {
176 signed = true OR false; /* default false */
177 byte_order = native OR network OR be OR le; /* default native */
178 size = value; /* value in bits, no default */
179 align = value; /* value in bits */
180 }
181
182 Example of type inheritance (creation of a uint32_t named type):
183
184 typealias integer {
185 size = 32;
186 signed = false;
187 align = 32;
188 } : uint32_t;
189
190 Definition of a named 5-bit signed bitfield:
191
192 typealias integer {
193 size = 5;
194 signed = true;
195 align = 1;
196 } : int5_t;
197
198 4.1.6 GNU/C bitfields
199
200 The GNU/C bitfields follow closely the integer representation, with a
201 particularity on alignment: if a bitfield cannot fit in the current unit, the
202 unit is padded and the bitfield starts at the following unit. The unit size is
203 defined by the size of the type "unit_type".
204
205 Metadata representation:
206
207 unit_type name:size:
208
209 As an example, the following structure declared in C compiled by GCC:
210
211 struct example {
212 short a:12;
213 short b:5;
214 };
215
216 The example structure is aligned on the largest element (short). The second
217 bitfield would be aligned on the next unit boundary, because it would not fit in
218 the current unit.
219
220 4.1.7 Floating point
221
222 The floating point values byte ordering is defined in the metadata.
223
224 Floating point values follow the IEEE 754-2008 standard interchange formats.
225 Description of the floating point values include the exponent and mantissa size
226 in bits. Some requirements are imposed on the floating point values:
227
228 - FLT_RADIX must be 2.
229 - mant_dig is the number of digits represented in the mantissa. It is specified
230 by the ISO C99 standard, section 5.2.4, as FLT_MANT_DIG, DBL_MANT_DIG and
231 LDBL_MANT_DIG as defined by <float.h>.
232 - exp_dig is the number of digits represented in the exponent. Given that
233 mant_dig is one bit more than its actual size in bits (leading 1 is not
234 needed) and also given that the sign bit always takes one bit, exp_dig can be
235 specified as:
236
237 - sizeof(float) * CHAR_BIT - FLT_MANT_DIG
238 - sizeof(double) * CHAR_BIT - DBL_MANT_DIG
239 - sizeof(long double) * CHAR_BIT - LDBL_MANT_DIG
240
241 Metadata representation:
242
243 floating_point {
244 exp_dig = value;
245 mant_dig = value;
246 byte_order = native OR network OR be OR le;
247 }
248
249 Example of type inheritance:
250
251 typealias floating_point {
252 exp_dig = 8; /* sizeof(float) * CHAR_BIT - FLT_MANT_DIG */
253 mant_dig = 24; /* FLT_MANT_DIG */
254 byte_order = native;
255 } : float;
256
257 TODO: define NaN, +inf, -inf behavior.
258
259 4.1.8 Enumerations
260
261 Enumerations are a mapping between an integer type and a table of strings. The
262 numerical representation of the enumeration follows the integer type specified
263 by the metadata. The enumeration mapping table is detailed in the enumeration
264 description within the metadata. The mapping table maps inclusive value ranges
265 (or single values) to strings. Instead of being limited to simple
266 "value -> string" mappings, these enumerations map
267 "[ start_value ... end_value ] -> string", which map inclusive ranges of
268 values to strings. An enumeration from the C language can be represented in
269 this format by having the same start_value and end_value for each element, which
270 is in fact a range of size 1. This single-value range is supported without
271 repeating the start and end values with the value = string declaration.
272
273 If a numeric value is encountered between < >, it represents the integer type
274 size used to hold the enumeration, in bits.
275
276 enum name <integer_type OR size> {
277 somestring = start_value1 ... end_value1,
278 "other string" = start_value2 ... end_value2,
279 yet_another_string, /* will be assigned to end_value2 + 1 */
280 "some other string" = value,
281 ...
282 };
283
284 If the values are omitted, the enumeration starts at 0 and increment of 1 for
285 each entry:
286
287 enum name <32> {
288 ZERO,
289 ONE,
290 TWO,
291 TEN = 10,
292 ELEVEN,
293 };
294
295 Overlapping ranges within a single enumeration are implementation defined.
296
297 A nameless enumeration can be declared as a field type or as part of a typedef:
298
299 enum <integer_type> {
300 ...
301 }
302
303
304 4.2 Compound types
305
306 Compound are aggregation of type declarations. Compound types include
307 structures, variant, arrays, sequences, and strings.
308
309 4.2.1 Structures
310
311 Structures are aligned on the largest alignment required by basic types
312 contained within the structure. (This follows the ISO/C standard for structures)
313
314 Metadata representation of a named structure:
315
316 struct name {
317 field_type field_name;
318 field_type field_name;
319 ...
320 };
321
322 Example:
323
324 struct example {
325 integer { /* Nameless type */
326 size = 16;
327 signed = true;
328 align = 16;
329 } first_field_name;
330 uint64_t second_field_name; /* Named type declared in the metadata */
331 };
332
333 The fields are placed in a sequence next to each other. They each possess a
334 field name, which is a unique identifier within the structure.
335
336 A nameless structure can be declared as a field type or as part of a typedef:
337
338 struct {
339 ...
340 }
341
342 4.2.2 Variants (Discriminated/Tagged Unions)
343
344 A CTF variant is a selection between different types. A CTF variant must
345 always be defined within the scope of a structure or within fields
346 contained within a structure (defined recursively). A "tag" enumeration
347 field must appear in either the same lexical scope, prior to the variant
348 field (in field declaration order), in an uppermost lexical scope (see
349 Section 7.2.1), or in an uppermost dynamic scope (see Section 7.2.2).
350 The type selection is indicated by the mapping from the enumeration
351 value to the string used as variant type selector. The field to use as
352 tag is specified by the "tag_field", specified between "< >" after the
353 "variant" keyword for unnamed variants, and after "variant name" for
354 named variants.
355
356 The alignment of the variant is the alignment of the type as selected by the tag
357 value for the specific instance of the variant. The alignment of the type
358 containing the variant is independent of the variant alignment. The size of the
359 variant is the size as selected by the tag value for the specific instance of
360 the variant.
361
362 A named variant declaration followed by its definition within a structure
363 declaration:
364
365 variant name {
366 field_type sel1;
367 field_type sel2;
368 field_type sel3;
369 ...
370 };
371
372 struct {
373 enum <integer_type or size> { sel1, sel2, sel3, ... } tag_field;
374 ...
375 variant name <tag_field> v;
376 }
377
378 An unnamed variant definition within a structure is expressed by the following
379 metadata:
380
381 struct {
382 enum <integer_type or size> { sel1, sel2, sel3, ... } tag_field;
383 ...
384 variant <tag_field> {
385 field_type sel1;
386 field_type sel2;
387 field_type sel3;
388 ...
389 } v;
390 }
391
392 Example of a named variant within a sequence that refers to a single tag field:
393
394 variant example {
395 uint32_t a;
396 uint64_t b;
397 short c;
398 };
399
400 struct {
401 enum <uint2_t> { a, b, c } choice;
402 variant example <choice> v[unsigned int];
403 }
404
405 Example of an unnamed variant:
406
407 struct {
408 enum <uint2_t> { a, b, c, d } choice;
409 /* Unrelated fields can be added between the variant and its tag */
410 int32_t somevalue;
411 variant <choice> {
412 uint32_t a;
413 uint64_t b;
414 short c;
415 struct {
416 unsigned int field1;
417 uint64_t field2;
418 } d;
419 } s;
420 }
421
422 Example of an unnamed variant within an array:
423
424 struct {
425 enum <uint2_t> { a, b, c } choice;
426 variant <choice> {
427 uint32_t a;
428 uint64_t b;
429 short c;
430 } v[10];
431 }
432
433 Example of a variant type definition within a structure, where the defined type
434 is then declared within an array of structures. This variant refers to a tag
435 located in an upper lexical scope. This example clearly shows that a variant
436 type definition referring to the tag "x" uses the closest preceding field from
437 the lexical scope of the type definition.
438
439 struct {
440 enum <uint2_t> { a, b, c, d } x;
441
442 typedef variant <x> { /*
443 * "x" refers to the preceding "x" enumeration in the
444 * lexical scope of the type definition.
445 */
446 uint32_t a;
447 uint64_t b;
448 short c;
449 } example_variant;
450
451 struct {
452 enum <int> { x, y, z } x; /* This enumeration is not used by "v". */
453 example_variant v; /*
454 * "v" uses the "enum <uint2_t> { a, b, c, d }"
455 * tag.
456 */
457 } a[10];
458 }
459
460 4.2.3 Arrays
461
462 Arrays are fixed-length. Their length is declared in the type declaration within
463 the metadata. They contain an array of "inner type" elements, which can refer to
464 any type not containing the type of the array being declared (no circular
465 dependency). The length is the number of elements in an array.
466
467 Metadata representation of a named array:
468
469 typedef elem_type name[length];
470
471 A nameless array can be declared as a field type within a structure, e.g.:
472
473 uint8_t field_name[10];
474
475
476 4.2.4 Sequences
477
478 Sequences are dynamically-sized arrays. They start with an integer that specify
479 the length of the sequence, followed by an array of "inner type" elements.
480 The length is the number of elements in the sequence.
481
482 Metadata representation for a named sequence:
483
484 typedef elem_type name[length_type];
485
486 A nameless sequence can be declared as a field type, e.g.:
487
488 long field_name[int];
489
490 The length type follows the integer types specifications, and the sequence
491 elements follow the "array" specifications.
492
493 4.2.5 Strings
494
495 Strings are an array of bytes of variable size and are terminated by a '\0'
496 "NULL" character. Their encoding is described in the metadata. In absence of
497 encoding attribute information, the default encoding is UTF-8.
498
499 Metadata representation of a named string type:
500
501 typealias string {
502 encoding = UTF8 OR ASCII;
503 } : name;
504
505 A nameless string type can be declared as a field type:
506
507 string field_name; /* Use default UTF8 encoding */
508
509 5. Event Packet Header
510
511 The event packet header consists of two part: one is mandatory and have a fixed
512 layout. The second part, the "event packet context", has its layout described in
513 the metadata.
514
515 - Aligned on page size. Fixed size. Fields either aligned or packed (depending
516 on the architecture preference).
517 No padding at the end of the event packet header. Native architecture byte
518 ordering.
519
520 Fixed layout (event packet header):
521
522 - Magic number (CTF magic numbers: 0xC1FC1FC1 and its reverse endianness
523 representation: 0xC11FFCC1) It needs to have a non-symmetric bytewise
524 representation. Used to distinguish between big and little endian traces (this
525 information is determined by knowing the endianness of the architecture
526 reading the trace and comparing the magic number against its value and the
527 reverse, 0xC11FFCC1). This magic number specifies that we use the CTF metadata
528 description language described in this document. Different magic numbers
529 should be used for other metadata description languages.
530 - Trace UUID, used to ensure the event packet match the metadata used.
531 (note: we cannot use a metadata checksum because metadata can be appended to
532 while tracing is active)
533 - Stream ID, used as reference to stream description in metadata.
534
535 Metadata-defined layout (event packet context):
536
537 - Event packet content size (in bytes).
538 - Event packet size (in bytes, includes padding).
539 - Event packet content checksum (optional). Checksum excludes the event packet
540 header.
541 - Per-stream event packet sequence count (to deal with UDP packet loss). The
542 number of significant sequence counter bits should also be present, so
543 wrap-arounds are deal with correctly.
544 - Timestamp at the beginning and timestamp at the end of the event packet.
545 Both timestamps are written in the packet header, but sampled respectively
546 while (or before) writing the first event and while (or after) writing the
547 last event in the packet. The inclusive range between these timestamps should
548 include all event timestamps assigned to events contained within the packet.
549 - Events discarded count
550 - Snapshot of a per-stream free-running counter, counting the number of
551 events discarded that were supposed to be written in the stream prior to
552 the first event in the event packet.
553 * Note: producer-consumer buffer full condition should fill the current
554 event packet with padding so we know exactly where events have been
555 discarded.
556 - Lossless compression scheme used for the event packet content. Applied
557 directly to raw data. New types of compression can be added in following
558 versions of the format.
559 0: no compression scheme
560 1: bzip2
561 2: gzip
562 3: xz
563 - Cypher used for the event packet content. Applied after compression.
564 0: no encryption
565 1: AES
566 - Checksum scheme used for the event packet content. Applied after encryption.
567 0: no checksum
568 1: md5
569 2: sha1
570 3: crc32
571
572 5.1 Event Packet Header Fixed Layout Description
573
574 struct event_packet_header {
575 uint32_t magic;
576 uint8_t trace_uuid[16];
577 uint32_t stream_id;
578 };
579
580 5.2 Event Packet Context Description
581
582 Event packet context example. These are declared within the stream declaration
583 in the metadata. All these fields are optional except for "content_size" and
584 "packet_size", which must be present in the context.
585
586 An example event packet context type:
587
588 struct event_packet_context {
589 uint64_t timestamp_begin;
590 uint64_t timestamp_end;
591 uint32_t checksum;
592 uint32_t stream_packet_count;
593 uint32_t events_discarded;
594 uint32_t cpu_id;
595 uint32_t/uint16_t content_size;
596 uint32_t/uint16_t packet_size;
597 uint8_t stream_packet_count_bits; /* Significant counter bits */
598 uint8_t compression_scheme;
599 uint8_t encryption_scheme;
600 uint8_t checksum_scheme;
601 };
602
603
604 6. Event Structure
605
606 The overall structure of an event is:
607
608 1 - Stream Packet Context (as specified by the stream metadata)
609 2 - Event Header (as specified by the stream metadata)
610 3 - Stream Event Context (as specified by the stream metadata)
611 4 - Event Context (as specified by the event metadata)
612 5 - Event Payload (as specified by the event metadata)
613
614 This structure defines an implicit dynamic scoping, where variants
615 located in inner structures (those with a higher number in the listing
616 above) can refer to the fields of outer structures (with lower number in
617 the listing above). See Section 7.2 Metadata Scopes for more detail.
618
619 6.1 Event Header
620
621 Event headers can be described within the metadata. We hereby propose, as an
622 example, two types of events headers. Type 1 accommodates streams with less than
623 31 event IDs. Type 2 accommodates streams with 31 or more event IDs.
624
625 One major factor can vary between streams: the number of event IDs assigned to
626 a stream. Luckily, this information tends to stay relatively constant (modulo
627 event registration while trace is being recorded), so we can specify different
628 representations for streams containing few event IDs and streams containing
629 many event IDs, so we end up representing the event ID and timestamp as densely
630 as possible in each case.
631
632 The header is extended in the rare occasions where the information cannot be
633 represented in the ranges available in the standard event header. They are also
634 used in the rare occasions where the data required for a field could not be
635 collected: the flag corresponding to the missing field within the missing_fields
636 array is then set to 1.
637
638 Types uintX_t represent an X-bit unsigned integer.
639
640
641 6.1.1 Type 1 - Few event IDs
642
643 - Aligned on 32-bit (or 8-bit if byte-packed, depending on the architecture
644 preference).
645 - Native architecture byte ordering.
646 - For "compact" selection
647 - Fixed size: 32 bits.
648 - For "extended" selection
649 - Size depends on the architecture and variant alignment.
650
651 struct event_header_1 {
652 /*
653 * id: range: 0 - 30.
654 * id 31 is reserved to indicate an extended header.
655 */
656 enum <uint5_t> { compact = 0 ... 30, extended = 31 } id;
657 variant <id> {
658 struct {
659 uint27_t timestamp;
660 } compact;
661 struct {
662 uint32_t id; /* 32-bit event IDs */
663 uint64_t timestamp; /* 64-bit timestamps */
664 } extended;
665 } v;
666 };
667
668
669 6.1.2 Type 2 - Many event IDs
670
671 - Aligned on 16-bit (or 8-bit if byte-packed, depending on the architecture
672 preference).
673 - Native architecture byte ordering.
674 - For "compact" selection
675 - Size depends on the architecture and variant alignment.
676 - For "extended" selection
677 - Size depends on the architecture and variant alignment.
678
679 struct event_header_2 {
680 /*
681 * id: range: 0 - 65534.
682 * id 65535 is reserved to indicate an extended header.
683 */
684 enum <uint16_t> { compact = 0 ... 65534, extended = 65535 } id;
685 variant <id> {
686 struct {
687 uint32_t timestamp;
688 } compact;
689 struct {
690 uint32_t id; /* 32-bit event IDs */
691 uint64_t timestamp; /* 64-bit timestamps */
692 } extended;
693 } v;
694 };
695
696
697 6.2 Event Context
698
699 The event context contains information relative to the current event. The choice
700 and meaning of this information is specified by the metadata "stream" and
701 "event" information. The "stream" context is applied to all events within the
702 stream. The "stream" context structure follows the event header. The "event"
703 context is applied to specific events. Its structure follows the "stream"
704 context stucture.
705
706 An example of stream-level event context is to save the event payload size with
707 each event, or to save the current PID with each event. These are declared
708 within the stream declaration within the metadata:
709
710 stream {
711 ...
712 event {
713 ...
714 context := struct {
715 uint pid;
716 uint16_t payload_size;
717 };
718 }
719 };
720
721 An example of event-specific event context is to declare a bitmap of missing
722 fields, only appended after the stream event context if the extended event
723 header is selected. NR_FIELDS is the number of fields within the event (a
724 numeric value).
725
726 event {
727 context = struct {
728 variant <id> {
729 struct { } compact;
730 struct {
731 uint1_t missing_fields[NR_FIELDS]; /* missing event fields bitmap */
732 } extended;
733 } v;
734 };
735 ...
736 }
737
738 6.3 Event Payload
739
740 An event payload contains fields specific to a given event type. The fields
741 belonging to an event type are described in the event-specific metadata
742 within a structure type.
743
744 6.3.1 Padding
745
746 No padding at the end of the event payload. This differs from the ISO/C standard
747 for structures, but follows the CTF standard for structures. In a trace, even
748 though it makes sense to align the beginning of a structure, it really makes no
749 sense to add padding at the end of the structure, because structures are usually
750 not followed by a structure of the same type.
751
752 This trick can be done by adding a zero-length "end" field at the end of the C
753 structures, and by using the offset of this field rather than using sizeof()
754 when calculating the size of a structure (see Appendix "A. Helper macros").
755
756 6.3.2 Alignment
757
758 The event payload is aligned on the largest alignment required by types
759 contained within the payload. (This follows the ISO/C standard for structures)
760
761
762 7. Metadata
763
764 The meta-data is located in a stream identified by its name: "metadata".
765 It is made of "event packets", which each start with an event packet
766 header. The event type within the metadata stream have no event header
767 nor event context. Each event only contains a null-terminated "string"
768 payload, which is a metadata description entry. The events are packed
769 one next to another. Each event packet start with an event packet
770 header, which contains, amongst other fields, the magic number and trace
771 UUID. In the event packet header, the trace UUID is represented as an
772 array of bytes. Within the string-based metadata description, the trace
773 UUID is represented as a string of hexadecimal digits and dashes "-".
774
775 The metadata can be parsed by reading through the metadata strings,
776 skipping null-characters. Type names are made of a single identifier,
777 and can be surrounded by prefix/postfix. Text contained within "/*" and
778 "*/", as well as within "//" and end of line, are treated as comments.
779 Boolean values can be represented as true, TRUE, or 1 for true, and
780 false, FALSE, or 0 for false.
781
782
783 7.1 Declaration vs Definition
784
785 A declaration associates a layout to a type, without specifying where
786 this type is located in the event structure hierarchy (see Section 6).
787 This therefore includes typedef, typealias, as well as all type
788 specifiers. In certain circumstances (typedef, structure field and
789 variant field), a declaration is followed by a declarator, which specify
790 the newly defined type name (for typedef), or the field name (for
791 declarations located within structure and variants). Array and sequence,
792 declared with square brackets ("[" "]"), are part of the declarator,
793 similarly to C99. The enumeration type specifier and variant tag name
794 (both specified with "<" ">") are part of the type specifier.
795
796 A definition associates a type to a location in the event structure
797 hierarchy (see Section 6). This association is denoted by ":=", as shown
798 in Section 7.3.
799
800
801 7.2 Metadata Scopes
802
803 CTF metadata uses two different types of scoping: a lexical scope is
804 used for declarations and type definitions, and a dynamic scope is used
805 for variants references to tag fields.
806
807 7.2.1 Lexical Scope
808
809 Each of "trace", "stream", "event", "struct" and "variant" have their own
810 nestable declaration scope, within which types can be declared using "typedef"
811 and "typealias". A root declaration scope also contains all declarations
812 located outside of any of the aforementioned declarations. An inner
813 declaration scope can refer to type declared within its container
814 lexical scope prior to the inner declaration scope. Redefinition of a
815 typedef or typealias is not valid, although hiding an upper scope
816 typedef or typealias is allowed within a sub-scope.
817
818 7.2.2 Dynamic Scope
819
820 A dynamic scope consists in the lexical scope augmented with the
821 implicit event structure definition hierarchy presented at Section 6.
822 The dynamic scope is only used for variant tag definitions. It is used
823 at definition time to look up the location of the tag field associated
824 with a variant.
825
826 Therefore, variants in lower levels in the dynamic scope (e.g. event
827 context) can refer to a tag field located in upper levels (e.g. in the
828 event header) by specifying, in this case, the associated tag with
829 <header.field_name>. This allows, for instance, the event context to
830 define a variant referring to the "id" field of the event header as
831 selector.
832
833 The target dynamic scope must be specified explicitly when referring to
834 a field outside of the local static scope. The dynamic scope prefixes
835 are thus:
836
837 - Stream Packet Context: <stream.packet.context. >,
838 - Event Header: <stream.event.header. >,
839 - Stream Event Context: <stream.event.context. >,
840 - Event Context: <event.context. >,
841 - Event Payload: <event.fields. >.
842
843 Multiple declarations of the same field name within a single scope is
844 not valid. It is however valid to re-use the same field name in
845 different scopes. There is no possible conflict, because the dynamic
846 scope must be specified when a variant refers to a tag field located in
847 a different dynamic scope.
848
849 The information available in the dynamic scopes can be thought of as the
850 current tracing context. At trace production, information about the
851 current context is saved into the specified scope field levels. At trace
852 consumption, for each event, the current trace context is therefore
853 readable by accessing the upper dynamic scopes.
854
855
856 7.3 Metadata Examples
857
858 The grammar representing the CTF metadata is presented in
859 Appendix C. CTF Metadata Grammar. This section presents a rather ligher
860 reading that consists in examples of CTF metadata, with template values:
861
862 trace {
863 major = value; /* Trace format version */
864 minor = value;
865 uuid = "aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa"; /* Trace UUID */
866 word_size = value;
867 };
868
869 stream {
870 id = stream_id;
871 /* Type 1 - Few event IDs; Type 2 - Many event IDs. See section 6.1. */
872 event.header := event_header_1 OR event_header_2;
873 event.context := struct {
874 ...
875 };
876 packet.context := struct {
877 ...
878 };
879 };
880
881 event {
882 name = event_name;
883 id = value; /* Numeric identifier within the stream */
884 stream = stream_id;
885 context := struct {
886 ...
887 };
888 fields := struct {
889 ...
890 };
891 };
892
893 /* More detail on types in section 4. Types */
894
895 /*
896 * Named types:
897 *
898 * Type declarations behave similarly to the C standard.
899 */
900
901 typedef aliased_type_prefix aliased_type new_type aliased_type_postfix;
902
903 /* e.g.: typedef struct example new_type_name[10]; */
904
905 /*
906 * typealias
907 *
908 * The "typealias" declaration can be used to give a name (including
909 * prefix/postfix) to a type. It should also be used to map basic C types
910 * (float, int, unsigned long, ...) to a CTF type. Typealias is a superset of
911 * "typedef": it also allows assignment of a simple variable identifier to a
912 * type.
913 */
914
915 typealias type_class {
916 ...
917 } : new_type_prefix new_type new_type_postfix;
918
919 /*
920 * e.g.:
921 * typealias integer {
922 * size = 32;
923 * align = 32;
924 * signed = false;
925 * } : struct page *;
926 *
927 * typealias integer {
928 * size = 32;
929 * align = 32;
930 * signed = true;
931 * } : int;
932 */
933
934 struct name {
935 ...
936 };
937
938 variant name {
939 ...
940 };
941
942 enum name <integer_type or size> {
943 ...
944 };
945
946
947 /*
948 * Unnamed types, contained within compound type fields, typedef or typealias.
949 */
950
951 struct {
952 ...
953 }
954
955 variant {
956 ...
957 }
958
959 enum <integer_type or size> {
960 ...
961 }
962
963 typedef type new_type[length];
964
965 struct {
966 type field_name[length];
967 }
968
969 typedef type new_type[length_type];
970
971 struct {
972 type field_name[length_type];
973 }
974
975 integer {
976 ...
977 }
978
979 floating_point {
980 ...
981 }
982
983 struct {
984 integer_type field_name:size; /* GNU/C bitfield */
985 }
986
987 struct {
988 string field_name;
989 }
990
991
992 A. Helper macros
993
994 The two following macros keep track of the size of a GNU/C structure without
995 padding at the end by placing HEADER_END as the last field. A one byte end field
996 is used for C90 compatibility (C99 flexible arrays could be used here). Note
997 that this does not affect the effective structure size, which should always be
998 calculated with the header_sizeof() helper.
999
1000 #define HEADER_END char end_field
1001 #define header_sizeof(type) offsetof(typeof(type), end_field)
1002
1003
1004 B. Stream Header Rationale
1005
1006 An event stream is divided in contiguous event packets of variable size. These
1007 subdivisions allow the trace analyzer to perform a fast binary search by time
1008 within the stream (typically requiring to index only the event packet headers)
1009 without reading the whole stream. These subdivisions have a variable size to
1010 eliminate the need to transfer the event packet padding when partially filled
1011 event packets must be sent when streaming a trace for live viewing/analysis.
1012 An event packet can contain a certain amount of padding at the end. Dividing
1013 streams into event packets is also useful for network streaming over UDP and
1014 flight recorder mode tracing (a whole event packet can be swapped out of the
1015 buffer atomically for reading).
1016
1017 The stream header is repeated at the beginning of each event packet to allow
1018 flexibility in terms of:
1019
1020 - streaming support,
1021 - allowing arbitrary buffers to be discarded without making the trace
1022 unreadable,
1023 - allow UDP packet loss handling by either dealing with missing event packet
1024 or asking for re-transmission.
1025 - transparently support flight recorder mode,
1026 - transparently support crash dump.
1027
1028 The event stream header will therefore be referred to as the "event packet
1029 header" throughout the rest of this document.
1030
1031 C. CTF Metadata Grammar
1032
1033 /*
1034 * Common Trace Format (CTF) Metadata Grammar.
1035 *
1036 * Inspired from the C99 grammar:
1037 * http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1124.pdf (Annex A)
1038 *
1039 * Specialized for CTF needs by including only constant and declarations from
1040 * C99 (excluding function declarations), and by adding support for variants,
1041 * sequences and CTF-specific specifiers.
1042 */
1043
1044 1) Lexical grammar
1045
1046 1.1) Lexical elements
1047
1048 token:
1049 keyword
1050 identifier
1051 constant
1052 string-literal
1053 punctuator
1054
1055 1.2) Keywords
1056
1057 keyword: is one of
1058
1059 const
1060 char
1061 double
1062 enum
1063 event
1064 floating_point
1065 float
1066 integer
1067 int
1068 long
1069 short
1070 signed
1071 stream
1072 string
1073 struct
1074 trace
1075 typealias
1076 typedef
1077 unsigned
1078 variant
1079 void
1080 _Bool
1081 _Complex
1082 _Imaginary
1083
1084
1085 1.3) Identifiers
1086
1087 identifier:
1088 identifier-nondigit
1089 identifier identifier-nondigit
1090 identifier digit
1091
1092 identifier-nondigit:
1093 nondigit
1094 universal-character-name
1095 any other implementation-defined characters
1096
1097 nondigit:
1098 _
1099 [a-zA-Z] /* regular expression */
1100
1101 digit:
1102 [0-9] /* regular expression */
1103
1104 1.4) Universal character names
1105
1106 universal-character-name:
1107 \u hex-quad
1108 \U hex-quad hex-quad
1109
1110 hex-quad:
1111 hexadecimal-digit hexadecimal-digit hexadecimal-digit hexadecimal-digit
1112
1113 1.5) Constants
1114
1115 constant:
1116 integer-constant
1117 enumeration-constant
1118 character-constant
1119
1120 integer-constant:
1121 decimal-constant integer-suffix-opt
1122 octal-constant integer-suffix-opt
1123 hexadecimal-constant integer-suffix-opt
1124
1125 decimal-constant:
1126 nonzero-digit
1127 decimal-constant digit
1128
1129 octal-constant:
1130 0
1131 octal-constant octal-digit
1132
1133 hexadecimal-constant:
1134 hexadecimal-prefix hexadecimal-digit
1135 hexadecimal-constant hexadecimal-digit
1136
1137 hexadecimal-prefix:
1138 0x
1139 0X
1140
1141 nonzero-digit:
1142 [1-9]
1143
1144 integer-suffix:
1145 unsigned-suffix long-suffix-opt
1146 unsigned-suffix long-long-suffix
1147 long-suffix unsigned-suffix-opt
1148 long-long-suffix unsigned-suffix-opt
1149
1150 unsigned-suffix:
1151 u
1152 U
1153
1154 long-suffix:
1155 l
1156 L
1157
1158 long-long-suffix:
1159 ll
1160 LL
1161
1162 digit-sequence:
1163 digit
1164 digit-sequence digit
1165
1166 hexadecimal-digit-sequence:
1167 hexadecimal-digit
1168 hexadecimal-digit-sequence hexadecimal-digit
1169
1170 enumeration-constant:
1171 identifier
1172 string-literal
1173
1174 character-constant:
1175 ' c-char-sequence '
1176 L' c-char-sequence '
1177
1178 c-char-sequence:
1179 c-char
1180 c-char-sequence c-char
1181
1182 c-char:
1183 any member of source charset except single-quote ('), backslash
1184 (\), or new-line character.
1185 escape-sequence
1186
1187 escape-sequence:
1188 simple-escape-sequence
1189 octal-escape-sequence
1190 hexadecimal-escape-sequence
1191 universal-character-name
1192
1193 simple-escape-sequence: one of
1194 \' \" \? \\ \a \b \f \n \r \t \v
1195
1196 octal-escape-sequence:
1197 \ octal-digit
1198 \ octal-digit octal-digit
1199 \ octal-digit octal-digit octal-digit
1200
1201 hexadecimal-escape-sequence:
1202 \x hexadecimal-digit
1203 hexadecimal-escape-sequence hexadecimal-digit
1204
1205 1.6) String literals
1206
1207 string-literal:
1208 " s-char-sequence-opt "
1209 L" s-char-sequence-opt "
1210
1211 s-char-sequence:
1212 s-char
1213 s-char-sequence s-char
1214
1215 s-char:
1216 any member of source charset except double-quote ("), backslash
1217 (\), or new-line character.
1218 escape-sequence
1219
1220 1.7) Punctuators
1221
1222 punctuator: one of
1223 [ ] ( ) { } . -> * + - < > : ; ... = ,
1224
1225
1226 2) Phrase structure grammar
1227
1228 primary-expression:
1229 identifier
1230 constant
1231 string-literal
1232 ( unary-expression )
1233
1234 postfix-expression:
1235 primary-expression
1236 postfix-expression [ unary-expression ]
1237 postfix-expression . identifier
1238 postfix-expressoin -> identifier
1239
1240 unary-expression:
1241 postfix-expression
1242 unary-operator postfix-expression
1243
1244 unary-operator: one of
1245 + -
1246
1247 assignment-operator:
1248 =
1249
1250 type-assignment-operator:
1251 :=
1252
1253 constant-expression:
1254 unary-expression
1255
1256 constant-expression-range:
1257 constant-expression ... constant-expression
1258
1259 2.2) Declarations:
1260
1261 declaration:
1262 declaration-specifiers declarator-list-opt ;
1263 ctf-specifier ;
1264
1265 declaration-specifiers:
1266 storage-class-specifier declaration-specifiers-opt
1267 type-specifier declaration-specifiers-opt
1268 type-qualifier declaration-specifiers-opt
1269
1270 declarator-list:
1271 declarator
1272 declarator-list , declarator
1273
1274 abstract-declarator-list:
1275 abstract-declarator
1276 abstract-declarator-list , abstract-declarator
1277
1278 storage-class-specifier:
1279 typedef
1280
1281 type-specifier:
1282 void
1283 char
1284 short
1285 int
1286 long
1287 float
1288 double
1289 signed
1290 unsigned
1291 _Bool
1292 _Complex
1293 _Imaginary
1294 struct-specifier
1295 variant-specifier
1296 enum-specifier
1297 typedef-name
1298 ctf-type-specifier
1299
1300 struct-specifier:
1301 struct identifier-opt { struct-or-variant-declaration-list-opt }
1302 struct identifier
1303
1304 struct-or-variant-declaration-list:
1305 struct-or-variant-declaration
1306 struct-or-variant-declaration-list struct-or-variant-declaration
1307
1308 struct-or-variant-declaration:
1309 specifier-qualifier-list struct-or-variant-declarator-list ;
1310 declaration-specifiers storage-class-specifier declaration-specifiers declarator-list ;
1311 typealias declaration-specifiers abstract-declarator-list : declaration-specifiers abstract-declarator-list ;
1312 typealias declaration-specifiers abstract-declarator-list : declarator-list ;
1313
1314 specifier-qualifier-list:
1315 type-specifier specifier-qualifier-list-opt
1316 type-qualifier specifier-qualifier-list-opt
1317
1318 struct-or-variant-declarator-list:
1319 struct-or-variant-declarator
1320 struct-or-variant-declarator-list , struct-or-variant-declarator
1321
1322 struct-or-variant-declarator:
1323 declarator
1324 declarator-opt : constant-expression
1325
1326 variant-specifier:
1327 variant identifier-opt variant-tag-opt { struct-or-variant-declaration-list }
1328 variant identifier variant-tag
1329
1330 variant-tag:
1331 < identifier >
1332
1333 enum-specifier:
1334 enum identifier-opt { enumerator-list }
1335 enum identifier-opt { enumerator-list , }
1336 enum identifier
1337 enum identifier-opt < declaration-specifiers > { enumerator-list }
1338 enum identifier-opt < declaration-specifiers > { enumerator-list , }
1339 enum identifier < declaration-specifiers >
1340 enum identifier-opt < integer-constant > { enumerator-list }
1341 enum identifier-opt < integer-constant > { enumerator-list , }
1342 enum identifier < integer-constant >
1343
1344 enumerator-list:
1345 enumerator
1346 enumerator-list , enumerator
1347
1348 enumerator:
1349 enumeration-constant
1350 enumeration-constant = constant-expression
1351 enumeration-constant = constant-expression-range
1352
1353 type-qualifier:
1354 const
1355
1356 declarator:
1357 pointer-opt direct-declarator
1358
1359 direct-declarator:
1360 identifier
1361 ( declarator )
1362 direct-declarator [ type-specifier ]
1363 direct-declarator [ constant-expression ]
1364
1365 abstract-declarator:
1366 pointer-opt direct-abstract-declarator
1367
1368 direct-abstract-declarator:
1369 identifier-opt
1370 ( abstract-declarator )
1371 direct-abstract-declarator [ type-specifier ]
1372 direct-abstract-declarator [ constant-expression ]
1373 direct-abstract-declarator [ ]
1374
1375 pointer:
1376 * type-qualifier-list-opt
1377 * type-qualifier-list-opt pointer
1378
1379 type-qualifier-list:
1380 type-qualifier
1381 type-qualifier-list type-qualifier
1382
1383 typedef-name:
1384 identifier
1385
1386 2.3) CTF-specific declarations
1387
1388 ctf-specifier:
1389 event { ctf-assignment-expression-list-opt }
1390 stream { ctf-assignment-expression-list-opt }
1391 trace { ctf-assignment-expression-list-opt }
1392 typealias declaration-specifiers abstract-declarator-list : declaration-specifiers abstract-declarator-list ;
1393 typealias declaration-specifiers abstract-declarator-list : declarator-list ;
1394
1395 ctf-type-specifier:
1396 floating_point { ctf-assignment-expression-list-opt }
1397 integer { ctf-assignment-expression-list-opt }
1398 string { ctf-assignment-expression-list-opt }
1399
1400 ctf-assignment-expression-list:
1401 ctf-assignment-expression
1402 ctf-assignment-expression-list ; ctf-assignment-expression
1403
1404 ctf-assignment-expression:
1405 unary-expression assignment-operator unary-expression
1406 unary-expression type-assignment-operator type-specifier
1407 declaration-specifiers storage-class-specifier declaration-specifiers declarator-list
1408 typealias declaration-specifiers abstract-declarator-list : declaration-specifiers abstract-declarator-list
1409 typealias declaration-specifiers abstract-declarator-list : declarator-list
This page took 0.093027 seconds and 3 git commands to generate.