From: Mathieu Desnoyers Date: Wed, 8 Jun 2011 21:00:24 +0000 (-0400) Subject: update metadata packet header size vs content size X-Git-Tag: v1.8~28 X-Git-Url: http://git.efficios.com/?p=ctf.git;a=commitdiff_plain;h=ce2228dad513904652a2c0a6487a4cddbbe60d37;hp=b12919a589a631b26fb9eecd4bfbecefa7744bb4 update metadata packet header size vs content size Signed-off-by: Mathieu Desnoyers --- diff --git a/common-trace-format-proposal.txt b/common-trace-format-proposal.txt index 746d076..2ae5ac2 100644 --- a/common-trace-format-proposal.txt +++ b/common-trace-format-proposal.txt @@ -900,11 +900,11 @@ 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 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: +"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: struct metadata_packet_header { uint32_t magic; /* 0x75D11D57 */