From: "George Spelvin" <linux@horizon.com>
To: linux@horizon.com, ulrich.windl@rz.uni-regensburg.de
Cc: linux-kernel@vger.kernel.org, tglx@linutronix.de,
williams@redhat.com, zippel@linux-m68k.org
Subject: Re: [RFC][PATCH] Adjust SHIFT_PLL to improve NTP convergence.
Date: 7 May 2009 14:07:32 -0400 [thread overview]
Message-ID: <20090507180732.27407.qmail@science.horizon.com> (raw)
In-Reply-To: <4A02C2A7.4033.ED06D54@Ulrich.Windl.rkdvmks1.ngate.uni-regensburg.de>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1125 bytes --]
> IMHO, the "value" of calibration during boot is dubious (unless you just
> reboot a "hot" machine): Usually the machine is cold on reboot, and the
> oscillators will drift a lot initially. Depending on your environment,
> the temperatures inside your box may rise about 10°C or more within a
> few minutes.
> Maybe an experimental feature "recalibrate anytime (and as long as you'd
> like)" would be interesting...
Well, a couple of points come to mind:
- Rebooting hot is not all that unusual. Less so that with Windows, but
some of us install test kernels from time to time. :-)
- If you're calibrating the CPU against the PIT, they're often derived
via PLL from the same clock source, so the *ratio* is fixed, and thus
the calibration won't drift at all.
- If there were some mechanism to make the divisor consistent across
boots, that would be helpful. Imagine a file in /sys that I could
write with an absolute frequency at boot time as long as it was within
1000 ppm (0.1%) of the kernel's measurement.
Thinking about it, the third option seems the most useful. It's
basically a cleaned-up tickadj.
next prev parent reply other threads:[~2009-05-07 18:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-04 21:03 john stultz
2009-05-05 0:27 ` Rik van Riel
2009-05-06 14:46 ` George Spelvin
2009-05-06 15:44 ` John Stultz
2009-05-07 6:07 ` George Spelvin
2009-05-07 9:14 ` Ulrich Windl
2009-05-07 18:07 ` George Spelvin [this message]
2009-05-07 19:37 ` john stultz
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=20090507180732.27407.qmail@science.horizon.com \
--to=linux@horizon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=ulrich.windl@rz.uni-regensburg.de \
--cc=williams@redhat.com \
--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
all inboxes | Powered by JetHome®