* Yannick Brosseau ([email protected]) wrote: > Hi all, > > I'm writing a CTF writer for perf and I'm discovering that some > mandatory fields for a CTF trace are not documented. > We must call the time field "timestamp" and the id field mapping event > to their description must be "id".
Yes, but they are not mandatory. They can be left out entirely. > Looking at parser source code, we can find other field like that. > > Would it be interesting to add this information in the CTF spec? I've put these fields as "examples" in the CTF spec, thinking that some would evolve into fixed field names in the future as usage confirms that it's indeed the right choice. > Or > should we write a second spec on the side for that kind of information? > The question we want to answer is "What do I need to put in a CTF file > to make it possible for a viewer to display it?" Beware though: a viewer could view a trace that lacks event ID and timestamp fields entirely. It would be limited to a single even type, and timestamp would always appear as 0. Thanks, Mathieu > > Yannick > > _______________________________________________ > lttng-dev mailing list > [email protected] > http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev -- Mathieu Desnoyers EfficiOS Inc. http://www.efficios.com _______________________________________________ lttng-dev mailing list [email protected] http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
