diff options
| author | Thomas Gleixner <tglx@kernel.org> | 2026-07-05 14:38:04 +0200 |
|---|---|---|
| committer | Thomas Gleixner <tglx@kernel.org> | 2026-07-06 17:47:44 +0200 |
| commit | e2904ddb14a4198ad31eb12a072a6923f0c8ca09 (patch) | |
| tree | 3d502736fd652140684e4dc057a433d74d365b08 /scripts/const_structs.checkpatch | |
| parent | a73d7f98e41a96d6e1bcb0e731ab185d9d67878e (diff) | |
| download | linux-e2904ddb14a4198ad31eb12a072a6923f0c8ca09.tar.gz linux-e2904ddb14a4198ad31eb12a072a6923f0c8ca09.zip | |
timekeeping: Document monotonic raw timestamps in snapshots correctly
The comments related to raw monotonic timestamps for the various
snapshot mechanisms in code and struct documentation are ambiguous. They
reference them as CLOCK_MONOTONIC_RAW timestamps, but with the arrival
of AUX clocks that's not longer correct.
The raw monotonic timestamps only represent CLOCK_MONOTONIC_RAW for the
system time clock IDs, i.e. REALTIME, MONOTONIC, BOOTTIME, TAI.
For AUX clocks they refer to the monotonic raw clock which is related to
the individual AUX clocks. These monotonic raw timestamps have the same
conversion factor as CLOCK_MONOTONIC_RAW, but differ from that by an
offset:
MONORAW(AUX$N) = MONORAW(SYSTEM) + OFFSET(AUX$N)
The offset is established when a AUX clock is enabled and stays constant
for the lifetime of the AUX clock.
Update the comments so they reflect reality.
Reported-by: Thomas Weißschuh <thomas.weissschuh@linutronix.de>
Signed-off-by: Thomas Gleixner <tglx@kernel.org>
Reviewed-by: Thomas Weißschuh <thomas.weissschuh@linutronix.de>
Link: https://patch.msgid.link/87wlv9k3wz.ffs@fw13
Diffstat (limited to 'scripts/const_structs.checkpatch')
0 files changed, 0 insertions, 0 deletions
