Return-Path: DKIM-Filter: OpenDKIM Filter v2.10.3 mail.efficios.com C17FD2E6339 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=efficios.com; s=default; t=1595515515; bh=ghB4AnWMPuRa7Pvj3I8PSFPIW7h7IeuNzedVm61+law=; h=From:To:Date:Message-Id; b=I4aq58+bYwuUQUshV7So+GJMADWERrL+1qvBlNVdixfm4t71YlhkbgstfhSPvmrUs Rw59yl/wOji5pv5mUk1pr971ZBFK9Pooc4siFtts6vYar0CrZ4QacheijEjA7CQ9Rx 6Lx4F90R2BSd6Y/QrrfMbnNi6yr+DRY1v2/yZ0CsE8ldR/blJc9p6LqNbhcHWGfTWn t/6Me6p5iBWOLfyMUB6jIRwvGvDBl2zHq2DNKTYO+UhAif7jMEpXqmUWYNTEOjXTx5 OXy/UaL4mz7/hlr7bKdICZ6UNmc729E0KT9ywk/8cqnsSnmdxIFWSmoh6OQBiOczgc bv0NZIrc1/aWQ== From: Mathieu Desnoyers Date: Thu, 23 Jul 2020 10:45:03 -0400 Message-Id: <20200723144503.5477-1-mathieu.desnoyers@efficios.com> Subject: [diamon-discuss] [RFC PATCH CTF] Clarify signedness of clock offset_s and offset fields List-Id: DiaMon diagnostic and monitoring workgroup general discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: diamon-discuss@lists.linuxfoundation.org Cc: Jeremie Galarneau , lttng-dev@lists.lttng.org, Genevieve Bastien Clarify that both offset_s and offset fields of clock may have negative values. Signed-off-by: Mathieu Desnoyers --- common-trace-format-specification.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/common-trace-format-specification.md b/common-trace-format-specification.md index b40082c..d4c69ad 100644 --- a/common-trace-format-specification.md +++ b/common-trace-format-specification.md @@ -1545,11 +1545,11 @@ The `offset_s` and `offset` fields indicate the offset from POSIX.1 Epoch, 1970-01-01 00:00:00 +0000 (UTC), to the zero of value of the clock. The `offset_s` field is in seconds. The `offset` field is in (1/freq) units. If any of the `offset_s` or `offset` field is not -present, it is assigned the 0 value. The field `absolute` is `TRUE` if -the clock is a global reference across different clock UUID -(e.g. NTP time). Otherwise, `absolute` is `FALSE`, and the clock can -be considered as synchronized only with other clocks that have the same -UUID. +present, it is assigned the 0 value. Both `offset_s` and `offset` +fields are signed integers. The field `absolute` is `TRUE` if the clock +is a global reference across different clock UUID (e.g. NTP time). +Otherwise, `absolute` is `FALSE`, and the clock can be considered as +synchronized only with other clocks that have the same UUID. Secondly, a reference to this clock should be added within an integer type: -- 2.11.0