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