Cleanup: update alignment of TOC

[ctf.git] / common-trace-format-specification.txt

diff --git a/common-trace-format-specification.txt b/common-trace-format-specification.txt
index 00ffe4a81ae8dbf571e28bd5335766562be03979..4af2244ab37adfa5a513cff029811cbdcc48bcea 100644 (file)
--- a/common-trace-format-specification.txt
+++ b/common-trace-format-specification.txt
@@ -41,12 +41,12 @@ Table of Contents
        4.1.6 GNU/C bitfields
        4.1.7 Floating point
        4.1.8 Enumerations
        4.1.6 GNU/C bitfields
        4.1.7 Floating point
        4.1.8 Enumerations

-4.2 Compound types
-    4.2.1 Structures
-    4.2.2 Variants (Discriminated/Tagged Unions)
-    4.2.3 Arrays
-    4.2.4 Sequences
-    4.2.5 Strings
+   4.2 Compound types
+       4.2.1 Structures
+       4.2.2 Variants (Discriminated/Tagged Unions)
+       4.2.3 Arrays
+       4.2.4 Sequences
+       4.2.5 Strings

 5. Event Packet Header
    5.1 Event Packet Header Description
    5.2 Event Packet Context Description
 5. Event Packet Header
    5.1 Event Packet Header Description
    5.2 Event Packet Context Description


@@ -816,6 +816,12 @@ located in inner structures (those with a higher number in the listing
 above) can refer to the fields of outer structures (with lower number in
 the listing above). See Section 7.3 TSDL Scopes for more detail.
 
 above) can refer to the fields of outer structures (with lower number in
 the listing above). See Section 7.3 TSDL Scopes for more detail.
 

+The total length of an event is defined as the difference between the
+end of its Event Payload and the end of the previous event's Event
+Payload. Therefore, it includes the event header alignment padding, and
+all its fields and their respective alignment padding. Events of length
+0 are forbidden.
+

 6.1 Event Header
 
 Event headers can be described within the meta-data. We hereby propose, as an
 6.1 Event Header
 
 Event headers can be described within the meta-data. We hereby propose, as an