From: Mathieu Desnoyers Date: Fri, 18 May 2012 20:19:27 +0000 (-0400) Subject: Clarify metadata sequence X-Git-Tag: v1.8.2~4 X-Git-Url: http://git.efficios.com/?p=ctf.git;a=commitdiff_plain;h=46400bde253c50d554b28b4635eea853c05dea45 Clarify metadata sequence Signed-off-by: Mathieu Desnoyers --- diff --git a/common-trace-format-specification.txt b/common-trace-format-specification.txt index 3130d98..331b9da 100644 --- a/common-trace-format-specification.txt +++ b/common-trace-format-specification.txt @@ -973,12 +973,13 @@ beginning of the file. This magic number is also used to detect the endianness of the architecture by trying to read the CTF magic number and its counterpart in reversed endianness. The events within the meta-data stream have no event header nor event context. Each event only -contains a "sequence" payload, which is a sequence of bits using the -"trace.packet.header.content_size" field as a placeholder for its length -(the packet header size should be substracted). The formatting of this -sequence of bits is a plain-text representation of the TSDL description. -Each meta-data packet start with a special packet header, specific to -the meta-data stream, which contains, exactly: +contains a special "sequence" payload, which is a sequence of bits which +length is implicitly calculated by using the +"trace.packet.header.content_size" field, minus the packet header size. +The formatting of this sequence of bits is a plain-text representation +of the TSDL description. Each meta-data packet start with a special +packet header, specific to the meta-data stream, which contains, +exactly: struct metadata_packet_header { uint32_t magic; /* 0x75D11D57 */