[RFC PATCH CTF] Clarify signedness of clock offset_s and offset fields

* [RFC PATCH CTF] Clarify signedness of clock offset_s and offset fields
@ 2020-07-23 14:45 Mathieu Desnoyers via lttng-dev
  2020-07-23 14:45 ` [lttng-dev] " Mathieu Desnoyers via lttng-dev
  0 siblings, 1 reply; 2+ messages in thread
From: Mathieu Desnoyers via lttng-dev @ 2020-07-23 14:45 UTC (permalink / raw)
  To: diamon-discuss
  Cc: Jeremie Galarneau, lttng-dev, Philippe Proulx, Genevieve Bastien

Clarify that both offset_s and offset fields of clock may have
negative values.

Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
---
 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

^ permalink raw reply related	[flat|nested] 2+ messages in thread