From: Linus Torvalds <torvalds@osdl.org>
To: Tim Bird <tim.bird@am.sony.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: get_cmos_time() takes up to a second on boot
Date: Fri, 7 May 2004 19:15:53 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0405071908060.3271@ppc970.osdl.org> (raw)
In-Reply-To: <409C2CBA.8040709@am.sony.com>
On Fri, 7 May 2004, Tim Bird wrote:
>
> What is the downside of disabling this
> synchronization with the clock edge?
It might not matter any more, but if I remember correctly, the real
problem was that we used to always write back the time to the CMOS clock
too, and then booting a few times and consistently getting the time wrong
the same way made the clock drift quite noticeably.
These days, I think we do the write-back only if we use an external clock
(NTP), so we probably _could_ just remove the synchronization at
read-time (removing it at write-time doesn't sound like a good idea).
Does anybody remember better?
> 1 second of variability is unnacceptable
> when you're requirement is to boot in
> .5 seconds. :)
Heh. And yes, it could be handled other ways (you could check the cmos
time in the timer interrupt during boot, and correct it there rather than
busy-waiting).
> Would it be bad to disable this synchronization
> completely? How about just during boot?
I don't think we should necessarily disable the synchronization, but we
could certainly make it optional for cases that don't care about it. We
might even make the default be "don't care about the read
synchronization".
Linus
next prev parent reply other threads:[~2004-05-08 2:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-08 0:41 Tim Bird
2004-05-08 2:15 ` Linus Torvalds [this message]
2004-05-10 6:05 ` Matthias Urlichs
2004-05-10 10:52 ` Gabriel Paubert
2004-05-10 11:53 ` Andries Brouwer
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=Pine.LNX.4.58.0405071908060.3271@ppc970.osdl.org \
--to=torvalds@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tim.bird@am.sony.com \
/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
all inboxes | Powered by JetHome®