linux-kernel - Re: [Y2038] [PATCH] drm/sti: Use 64-bit timestamps

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] [day] [month] [year] [list]

Message-ID: <10365926.7cr9Md2xG1@wuerfel>
Date:	Mon, 18 Apr 2016 12:32:12 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	y2038@...ts.linaro.org
Cc:	Vincent ABRIOU <vincent.abriou@...com>,
	David Airlie <airlied@...ux.ie>,
	Benjamin Gaignard <benjamin.gaignard@...aro.org>,
	Tina Ruchandani <ruchandani.tina@...il.com>,
	"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [Y2038] [PATCH] drm/sti: Use 64-bit timestamps

On Monday 18 April 2016 12:02:35 Vincent ABRIOU wrote:
> 
> getrawmonotonic comes from a legacy code so the use is not intentional.
> Honestly, it is not clear to me the difference between monotonic and 
> rawmonotonic. But in the debug context in which it is used, ktime_get 
> and ktime_get_raw will deliver the same level of information we need. So 
> implementation done by Tina is fine for me.
> 

Ok, cool, thanks for confirming!

FWIW, the best way I can see for illustrating the difference is that
rawmonotonic time is for things that should be synchronized with the
machines clock generators (e.g. A/V sync), while monotonic time is
for the case where you want to synchronize with another machine (or
the internet) that may have a slightly different clock generator but
uses NTP to correct for that.

In most cases the difference is irrelevant and we tend to use monotonic
time by default.

	Arnd