From: Gabriel Paubert <paubert@iram.es>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Johannes Berg <johannes@sipsolutions.net>, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 2/3] powermac: proper time of day after resume
Date: Thu, 25 Jan 2007 12:09:51 +0100 [thread overview]
Message-ID: <20070125110951.GA31911@iram.es> (raw)
In-Reply-To: <2435847C-A9FC-4430-A122-416B9B347038@kernel.crashing.org>
On Wed, Jan 24, 2007 at 03:23:47PM +0100, Segher Boessenkool wrote:
> >I believed that the patch also worked on desktops. Of course, one
> >solution is to try to reset time from an NTP server on resume if you
> >are connected (if you are not, then an error of a fraction of a second
> >is less serious).
>
> A fraction of a second is *never* serious, except with
> broken apps ;-)
>
You've obviously never met people doing VLBI (Very Long Baseline
Interferometry) ;-)
Seriously, here we have a bunch of machines doing data acquisition
which are synchronized through timestamps taken at interrupt time.
They need an accuracy ot 5-10ms, which NTP easily provides (we have
our own redundant NTP servers connected to reference clocks: GPS
receivers and high precision clocks including an hydrogen maser).
Fortunately they never perform a suspend/resume cycle, because this
precision is not achievable even when trying to synchronize with the
second transition from the RTC.
If we did suspend the machines to save power, the only solution
would be to tell NTP to synchronize with the master clock by
stepping the time (not slewing) at resume time.
Gabriel
next prev parent reply other threads:[~2007-01-25 11:09 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-13 12:38 [PATCH 0/3] some preparations for suspend on G5 powermac Johannes Berg
2006-12-13 12:38 ` [PATCH 1/3] windfarm: dont die on suspend thread signal Johannes Berg
2007-01-24 6:32 ` Benjamin Herrenschmidt
2006-12-13 12:38 ` [PATCH 2/3] powermac: proper time of day after resume Johannes Berg
2007-01-24 6:34 ` Benjamin Herrenschmidt
2007-01-24 8:46 ` Johannes Berg
2007-01-24 8:51 ` Benjamin Herrenschmidt
2007-01-24 8:54 ` Gabriel Paubert
2007-01-24 9:32 ` Benjamin Herrenschmidt
2007-01-24 10:36 ` Gabriel Paubert
2007-01-24 14:23 ` Segher Boessenkool
2007-01-24 21:44 ` Benjamin Herrenschmidt
2007-01-24 22:24 ` Segher Boessenkool
2007-01-24 22:35 ` Benjamin Herrenschmidt
2007-01-24 23:21 ` Segher Boessenkool
2007-01-25 7:39 ` Michel Dänzer
2007-01-25 8:06 ` Benjamin Herrenschmidt
2007-01-25 8:10 ` Michel Dänzer
2007-01-25 11:09 ` Gabriel Paubert [this message]
2007-01-25 12:54 ` Johannes Berg
2007-01-26 14:35 ` Johannes Berg
2007-02-01 19:16 ` [PATCH] " Johannes Berg
2007-02-02 12:19 ` Johannes Berg
2007-02-03 2:41 ` Michael Ellerman
2007-02-03 17:37 ` Johannes Berg
2007-05-02 4:45 ` Paul Mackerras
2007-05-02 4:47 ` Paul Mackerras
2007-05-02 8:26 ` Johannes Berg
2007-05-02 14:25 ` [PATCH] powerpc timer sysdev: use mktime Johannes Berg
2007-05-23 15:28 ` Johannes Berg
2007-05-28 4:33 ` Paul Mackerras
2006-12-13 12:38 ` [PATCH 3/3] powerpc: fix comment in kernel/irq.c Johannes Berg
2006-12-13 13:13 ` Johannes Berg
2006-12-19 5:40 ` Paul Mackerras
2006-12-19 18:29 ` Johannes Berg
2007-01-24 6:35 ` Benjamin Herrenschmidt
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=20070125110951.GA31911@iram.es \
--to=paubert@iram.es \
--cc=johannes@sipsolutions.net \
--cc=linuxppc-dev@ozlabs.org \
--cc=segher@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).