Skip to content

RFC Common Trace Format Updates (upcoming 1.8.3)

Mathieu Desnoyers via lttng-dev diamon-discuss lttng-dev 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 RFC Latest3 patches 8 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/3Clarify that unlisted enum values are implementation-definedcommon-trace-format-specification.md+3 -06 replies
2/3Clarify monotonicity requirement on timestamp begincommon-trace-format-specification.md+6 -42 replies
3/3Clarify that timestamp begin/end need to be complete clock valuescommon-trace-format-specification.md+4 -30 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [RFC PATCH CTF 0/3] Common Trace Format Updates (upcoming 1.8.3)

Hi,

We noticed a few unspecified areas in the CTF 1.8.2 specification which require some clarifications. We therefore plan to do a 1.8.3 release of the specification including those changes.

Review is welcome,

Thanks,

Mathieu

Geneviève Bastien (1):
Clarify that unlisted enum values are implementation-defined

Mathieu Desnoyers (2):
Clarify monotonicity requirement on timestamp begin Clarify that timestamp begin/end need to be complete clock values

 common-trace-format-specification.md | 20 +++++++++++++-------
 1 file changed, 13 insertions(+), 7 deletions(-)
Signature · 6 lines
2.11.0

_______________________________________________
lttng-dev mailing list
[email protected]
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev