linux-kernel - Re: firewire: CLOCK_MONOTONIC

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 16 Jul 2014 13:34:21 +0200
From:	Clemens Ladisch <clemens@...isch.de>
To:	Thomas Gleixner <tglx@...utronix.de>,
	Stefan Richter <stefanr@...6.in-berlin.de>
CC:	linux-kernel@...r.kernel.org,
	linux1394-devel@...ts.sourceforge.net,
	Peter Zijlstra <peterz@...radead.org>,
	John Stultz <john.stultz@...aro.org>
Subject: Re: firewire: CLOCK_MONOTONIC_RAW exposure

Thomas Gleixner wrote:
> I wonder why firewire exposed CLOCK_MONOTONIC_RAW to user space.
>
> What's the purpose of that? CLOCK_MONOTONIC_RAW is the raw time based
> on the initial frequency setup of the clocksource. That can be quite
> off from the NTP corrected frequency which is exposed by
> CLOCK_MONOTONIC.

The purpose is to get a stable clock, i.e., to avoid clock rate changes
caused by NTP corrections.

ALSA is adding CLOCK_MONOTONIC_RAW for the same reason.


Regards,
Clemens
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/