From: Arnd Bergmann <arnd@arndb.de>
To: y2038@lists.linaro.org
Cc: Vincent ABRIOU <vincent.abriou@st.com>, David Airlie <airlied@linux.ie>,
        Benjamin Gaignard <benjamin.gaignard@linaro.org>,
        Tina Ruchandani <ruchandani.tina@gmail.com>,
        "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Y2038] [PATCH] drm/sti: Use 64-bit timestamps
Date: Mon, 18 Apr 2016 12:32:12 +0200
Message-ID: <10365926.7cr9Md2xG1@wuerfel>
User-Agent: KMail/4.11.5 (Linux/3.16.0-10-generic; KDE/4.11.5; x86_64; ; )
In-Reply-To: <5714B0BB.1020306@st.com>
References: <20160413092802.GA99759@localhost> <7376001.70fALvhWdv@wuerfel> <5714B0BB.1020306@st.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 906
Lines: 22

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