From: "H. Peter Anvin" <hpa@zytor.com>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>,
Marc Perkel <mperkel@yahoo.com>, Chris Snook <csnook@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: AMD Quad Core clock problem?
Date: Mon, 14 Apr 2008 18:24:46 -0700 [thread overview]
Message-ID: <480403DE.4070901@zytor.com> (raw)
In-Reply-To: <m3prsrj51j.fsf@maximus.localdomain>
Krzysztof Halasa wrote:
> lsorense@csclub.uwaterloo.ca (Lennart Sorensen) writes:
>
>> True, but usually they give you an option to turn it off in the BIOS to
>> make the system actually work with things like NTP.
>>
>> Maybe I should have said "Any system with spread spectrum enabled".
>
> I haven't investigated those spread spectrums at all but sometimes
> there are options: "center" (the frequency is centered around the
> nominal value, I guess) and "below" (or something like that). If done
> correctly, "center" shouldn't have visible effect on NTP, should it?
It shouldn't really matter, since "below" produces a similar spectrum at
a slightly lower frequency.
The main issue is how slow the frequency slew really is; typically the
slew should well average out to zero over the timescale that NTP cares
about.
> The other important question is "what frequency has spread spectrum
> enabled"? CPU (= TSC), HPET, RAM, something else?
In PCs, the TSC and RAM will be affected; the HPET, PMTMR and PIT are
fed from the 14.31818 MHz timekeeping crystal which is generally *not*
spread.
-hpa
next prev parent reply other threads:[~2008-04-15 1:25 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-11 18:27 AMD Quad Core clock problem? Marc Perkel
2008-04-11 18:35 ` H. Willstrand
2008-04-11 18:38 ` Chris Snook
2008-04-11 20:28 ` Marc Perkel
2008-04-11 21:11 ` Chris Snook
2008-04-11 21:36 ` Marc Perkel
2008-04-11 21:38 ` Lennart Sorensen
2008-04-13 19:35 ` H. Peter Anvin
2008-04-14 15:12 ` Lennart Sorensen
2008-04-14 16:23 ` H. Peter Anvin
2008-04-14 16:29 ` Lennart Sorensen
2008-04-15 1:11 ` Krzysztof Halasa
2008-04-15 1:24 ` H. Peter Anvin [this message]
2008-04-15 1:45 ` Krzysztof Halasa
2008-04-15 2:40 ` H. Peter Anvin
2008-04-11 21:46 ` Krzysztof Halasa
2008-04-11 22:09 ` Marc Perkel
2008-04-13 8:19 ` Bart Van Assche
2008-04-12 1:04 ` Marc Perkel
2008-04-14 19:16 ` Chris Snook
2008-04-14 20:46 ` Marc Perkel
2008-04-15 6:11 ` Bart Van Assche
2008-04-16 21:44 ` Marc Perkel
2008-04-17 6:17 ` Bart Van Assche
2008-04-17 18:03 ` Marc Perkel
2008-04-18 11:56 ` Bart Van Assche
2008-06-17 21:09 ` Marc Perkel
2008-04-14 13:40 ` Marc Perkel
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=480403DE.4070901@zytor.com \
--to=hpa@zytor.com \
--cc=csnook@redhat.com \
--cc=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
--cc=mperkel@yahoo.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