From: Timothy Miller <miller@techsource.com>
To: Tim Schmielau <tim@physik3.uni-rostock.de>
Cc: Patrick Moor <pmoor@netpeople.ch>,
lkml <linux-kernel@vger.kernel.org>,
george anzinger <george@mvista.com>
Subject: Re: time jumps (again)
Date: Wed, 06 Aug 2003 14:16:35 -0400 [thread overview]
Message-ID: <3F314603.7050907@techsource.com> (raw)
In-Reply-To: Pine.LNX.4.33.0308042347300.12309-100000@gans.physik3.uni-rostock.de
Is there any way the kernel could detect clock problems like drift and
jumps by comparing the effects of different timers? And when a problem
is detected, it can correct the situation automatically.
How many interrupt timers are there in various systems? How much can we
rely on the accuracy of each one?
next prev parent reply other threads:[~2003-08-06 18:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-04 16:35 time jumps (again) Patrick Moor
2003-08-04 16:37 ` Alan Cox
2003-08-04 21:49 ` Tim Schmielau
2003-08-04 22:38 ` george anzinger
2003-08-05 1:08 ` Andries Brouwer
2003-08-06 18:16 ` Timothy Miller [this message]
2003-08-06 18:55 ` George Anzinger
2003-08-07 0:29 ` Andries Brouwer
2003-08-05 10:32 ` Jan Niehusmann
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=3F314603.7050907@techsource.com \
--to=miller@techsource.com \
--cc=george@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pmoor@netpeople.ch \
--cc=tim@physik3.uni-rostock.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