From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: john stultz <johnstul@us.ibm.com>
Cc: Roman Zippel <zippel@linux-m68k.org>,
Ulrich Windl <ulrich.windl@rz.uni-regensburg.de>,
linux-kernel@vger.kernel.org,
Udo van den Heuvel <udovdh@xs4all.nl>
Subject: Re: Linux time code
Date: Thu, 17 Aug 2006 15:11:59 -0700 [thread overview]
Message-ID: <200608171512.00417.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <1155851917.31755.125.camel@cog.beaverton.ibm.com>
On Thursday, August 17, 2006 2:58 pm, john stultz wrote:
> On Thu, 2006-08-17 at 13:43 +0200, Roman Zippel wrote:
> > On Wed, 16 Aug 2006, john stultz wrote:
> > > > For example there is a POSIX-like sys_clock_gettime() intended
> > > > to server the end-user directly, but there's no counterpart
> > > > do_clock_gettime() to server any in-kernel needs.
> > >
> > > Hmmm.. ktime_get(), ktime_get_ts() and ktime_get_real(), provide
> > > this info. Is there something missing here?
> >
> > What is missing is the abiltity to map a clock to a posix clock, so
> > that you would have CLOCK_REALTIME/CLOCK_MONOTONIC as NTP controlled
> > clocks and other CLOCK_* as the raw clock.
>
> Is there a use case for this (wanting non-NTP corrected time on a
> system running NTPd) you have in mind?
Isn't this what CLOCK_MONOTONIC[_HR] is for? It's not supposed to jump
around at all, so the basic usage model is to use this source for
timestamping purposes...
Jesse
next prev parent reply other threads:[~2006-08-17 22:11 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-16 12:26 Ulrich Windl
2006-08-16 12:36 ` Oleg Verych
2006-08-16 15:35 ` H. Peter Anvin
2006-08-16 15:12 ` Oleg Verych
2006-08-16 19:53 ` john stultz
2006-08-17 7:20 ` Ulrich Windl
2006-08-17 19:15 ` john stultz
2006-08-17 11:43 ` Roman Zippel
2006-08-17 21:58 ` john stultz
2006-08-17 22:11 ` Jesse Barnes [this message]
2006-08-17 22:32 ` john stultz
2006-08-17 22:50 ` Jesse Barnes
2006-08-17 23:02 ` john stultz
2006-08-20 17:14 ` Roman Zippel
2006-08-20 17:10 ` Roman Zippel
2006-08-23 6:25 linux
2006-08-23 18:29 ` john stultz
2006-08-24 2:35 ` linux
2006-08-28 11:39 ` Roman Zippel
2006-08-28 22:36 ` john stultz
2006-08-29 3:28 ` linux
2006-08-29 13:15 ` Theodore Tso
2006-08-29 15:18 ` linux
2006-08-29 19:23 ` john stultz
2006-08-29 14:43 ` Roman Zippel
2006-08-26 0:17 ` linux
2006-08-28 22:41 ` john stultz
2006-08-26 3:46 ` linux
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=200608171512.00417.jbarnes@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=udovdh@xs4all.nl \
--cc=ulrich.windl@rz.uni-regensburg.de \
--cc=zippel@linux-m68k.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
Powered by JetHome