public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: James Courtier-Dutton <James@superbug.co.uk>
To: Christoph Lameter <clameter@engr.sgi.com>
Cc: john stultz <johnstul@us.ibm.com>,
	lkml <linux-kernel@vger.kernel.org>,
	Tim Schmielau <tim@physik3.uni-rostock.de>,
	George Anzinger <george@mvista.com>,
	albert@users.sourceforge.net,
	Ulrich Windl <ulrich.windl@rz.uni-regensburg.de>,
	Dominik Brodowski <linux@dominikbrodowski.de>,
	David Mosberger <davidm@hpl.hp.com>, Andi Kleen <ak@suse.de>,
	paulus@samba.org, schwidefsky@de.ibm.com,
	keith maanthey <kmannth@us.ibm.com>,
	Chris McDermott <lcm@us.ibm.com>, Max Asbock <masbock@us.ibm.com>,
	mahuja@us.ibm.com, Nishanth Aravamudan <nacc@us.ibm.com>,
	Darren Hart <darren@dvhart.com>,
	"Darrick J. Wong" <djwong@us.ibm.com>,
	Anton Blanchard <anton@samba.org>,
	donf@us.ibm.com, mpm@selenic.com, benh@kernel.crashing.org,
	linux-ia64@vger.kernel.org
Subject: Re: IA64 implementation of timesource for new time of day subsystem
Date: Sun, 15 May 2005 09:12:21 +0000	[thread overview]
Message-ID: <428722E3.6040202@superbug.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.62.0505141251490.18681@schroedinger.engr.sgi.com>

Christoph Lameter wrote:
> On Fri, 13 May 2005, john stultz wrote:
> 
> 
>>I look forward to your comments and feedback.
> 
> 
> Here is the implementation of the IA64 timesources for the new time of 
> day subsystem.
> 
> This is quite straighforward. Thanks John. However, the ITC
> interpolator can no longer use MMIO in SMP situations since there is no 
> provision for jitter compensation in the new time of day subsystem. I have
> implemented that via a function now which will slow down clock access
> for non SGI IA64 hardware significantly since it will not be able to use
> the fastcall anymore.
> 
> I am working on the fastcall but I would need a couple of changes
> to the core code to make the following symbols non-static since they
> will need to be accessed from the fast syscall handler:
> 
> timesource
> system_time
> wall_time_offset
> offset_base
> 

Will this mean that Linux will have a monotonic time source?
For media players we need a timesource that does not change under any
circumstances. e.g. User changes the clock time, the monotonic time
source should not change. The monotonic time source should just start at
0 at power on, and continually increase accurately over time. I.e. A
very accurate "uptime" measurement.

James

  reply	other threads:[~2005-05-15  9:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1116029796.26454.2.camel@cog.beaverton.ibm.com>
     [not found] ` <1116029872.26454.4.camel@cog.beaverton.ibm.com>
     [not found]   ` <1116029971.26454.7.camel@cog.beaverton.ibm.com>
     [not found]     ` <1116030058.26454.10.camel@cog.beaverton.ibm.com>
     [not found]       ` <1116030139.26454.13.camel@cog.beaverton.ibm.com>
2005-05-14 19:55         ` IA64 implementation of timesource for new time of day subsystem Christoph Lameter
2005-05-15  9:12           ` James Courtier-Dutton [this message]
2005-05-15 10:17             ` Andi Kleen
2005-05-16 15:30               ` Chris Friesen
2005-05-16 17:34           ` john stultz
2005-05-16 18:09             ` Christoph Lameter
2005-05-16 18:45               ` john stultz
2005-05-16 18:55                 ` john stultz
2005-05-16 19:24                 ` Christoph Lameter
2005-05-16 19:29                   ` David Mosberger
2005-05-16 19:50                     ` john stultz
2005-05-16 20:27                       ` Christoph Lameter
2005-05-16 20:53                         ` john stultz
2005-05-16 20:58                           ` David Mosberger
2005-05-16 21:35                             ` john stultz
2005-05-16 21:53                               ` Christoph Lameter
2005-05-17  8:05                     ` Ulrich Windl

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=428722E3.6040202@superbug.co.uk \
    --to=james@superbug.co.uk \
    --cc=ak@suse.de \
    --cc=albert@users.sourceforge.net \
    --cc=anton@samba.org \
    --cc=benh@kernel.crashing.org \
    --cc=clameter@engr.sgi.com \
    --cc=darren@dvhart.com \
    --cc=davidm@hpl.hp.com \
    --cc=djwong@us.ibm.com \
    --cc=donf@us.ibm.com \
    --cc=george@mvista.com \
    --cc=johnstul@us.ibm.com \
    --cc=kmannth@us.ibm.com \
    --cc=lcm@us.ibm.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@dominikbrodowski.de \
    --cc=mahuja@us.ibm.com \
    --cc=masbock@us.ibm.com \
    --cc=mpm@selenic.com \
    --cc=nacc@us.ibm.com \
    --cc=paulus@samba.org \
    --cc=schwidefsky@de.ibm.com \
    --cc=tim@physik3.uni-rostock.de \
    --cc=ulrich.windl@rz.uni-regensburg.de \
    /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