From: Pasi Savolainen <psavo@iki.fi>
To: linux-kernel@vger.kernel.org
Subject: Re: can TSC tick with different speeds on SMP?
Date: Mon, 21 Jun 2004 19:22:30 +0000 (UTC) [thread overview]
Message-ID: <slrncdedbm.a4u.psavo@varg.dyndns.org> (raw)
In-Reply-To: <E1BcU4I-000Cj2-00.kksx-mail-ru@f27.mail.ru>
* Kirill Korotaev <kksx@mail.ru>:
> Hello,
>
> I've got some stupid question to SMP gurus and would be very thankful
> for the details. I suddenly faced an SMP system where different P4 cpus
> were installed (with different steppings). This resulted in different
> CPU clock speeds and different speeds of time stamp counters on these
> CPUs. I faced the problem during some timings I measured in the kernel.
>
> So the question is "is such system compliant with SMP specification?".
Well, I can't tell if it's SMP-compliant, but I can tell that it's
certainly not rare to have such a situation.
For example on AMD K7-SMP system when using powersaving mode which
basically 'turns CPU off' for a while, TSC's become desynchronized. At
the moment 2.6 -kernels handle this very well. (I haven't got problems
with it for more than half a year).
Now, I don't know what will happen if the become desynchronized because
of totally different _length_ of single tick. Is this what you
experience?
FWIW, this is what I get for timer in dmesg:
- -
...
Using pmtmr for high-res timesource
...
Using local APIC timer interrupts.
calibrating APIC timer ...
..... CPU clock speed is 1545.0689 MHz.
..... host bus clock speed is 268.0815 MHz.
checking TSC synchronization across 2 CPUs: passed.
...
- -
--
Psi -- <http://www.iki.fi/pasi.savolainen>
next prev parent reply other threads:[~2004-06-21 19:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-21 19:02 "Kirill Korotaev"
2004-06-21 19:22 ` Pasi Savolainen [this message]
2004-06-21 19:32 ` Grzegorz Kulewski
2004-06-21 20:50 ` James Cleverdon
2004-06-21 21:09 ` Zwane Mwaikambo
2004-06-21 22:31 ` john stultz
[not found] <29Cl9-2Uu-13@gated-at.bofh.it>
2004-06-22 3:30 ` Andi Kleen
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=slrncdedbm.a4u.psavo@varg.dyndns.org \
--to=psavo@iki.fi \
--cc=linux-kernel@vger.kernel.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®