From 5ae2352de690f0a4d9b8ee4ae3d313af568b966c Mon Sep 17 00:00:00 2001 From: Mathieu Desnoyers Date: Mon, 16 May 2011 17:17:29 -0400 Subject: [PATCH 1/1] Update packet-based metadata description Signed-off-by: Mathieu Desnoyers --- common-trace-format-proposal.txt | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/common-trace-format-proposal.txt b/common-trace-format-proposal.txt index 238fbad..6974f7c 100644 --- a/common-trace-format-proposal.txt +++ b/common-trace-format-proposal.txt @@ -886,9 +886,12 @@ 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 "string" payload. Each meta-data packet start with a special -packet header, specific to the meta-data stream, which contains, -exactly: +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: struct metadata_packet_header { uint32_t magic; /* 0x75D11D57 */ -- 2.34.1