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 [thread overview]
Message-ID: <10365926.7cr9Md2xG1@wuerfel> (raw)
In-Reply-To: <5714B0BB.1020306@st.com>
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
prev parent reply other threads:[~2016-04-18 10:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-13 9:28 [PATCH] drm/sti: Use 64-bit timestamps Tina Ruchandani
2016-04-16 23:39 ` [Y2038] " Arnd Bergmann
2016-04-18 10:02 ` Vincent ABRIOU
2016-04-18 10:32 ` Arnd Bergmann [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=10365926.7cr9Md2xG1@wuerfel \
--to=arnd@arndb.de \
--cc=airlied@linux.ie \
--cc=benjamin.gaignard@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ruchandani.tina@gmail.com \
--cc=vincent.abriou@st.com \
--cc=y2038@lists.linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox