From: James Cleverdon <jamesclv@us.ibm.com>
To: "Kirill Korotaev" <kksx@mail.ru>, linux-kernel@vger.kernel.org
Subject: Re: can TSC tick with different speeds on SMP?
Date: Mon, 21 Jun 2004 13:50:09 -0700 [thread overview]
Message-ID: <200406211350.09295.jamesclv@us.ibm.com> (raw)
In-Reply-To: <E1BcU4I-000Cj2-00.kksx-mail-ru@f27.mail.ru>
IIRC, in the IA64 manuals Intel, by carefully not making any guarantees
to the contrary, reserved the right to have the TSC-equivalent register
not be synchronized either to the bus clock or the CPU clock.
This doesn't directly apply to IA32, but may give a hint as to their
future intentions.
On Monday 21 June 2004 12:02 pm, Kirill Korotaev wrote:
> 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?". In old kernels there was a code to syncronize TSCs
> and to detect if they were screwed up. Current kernels do not have
> such code. Is it intentional? I suppose there is some code in kernel
> which won't work find on such systems (real-time threads timing
> accounting and so on).
>
> Thanks in advance,
> Kirill
>
> -
>
--
James Cleverdon
IBM LTC (xSeries Linux Solutions)
{jamesclv(Unix, preferred), cleverdj(Notes)} at us dot ibm dot comm
next prev parent reply other threads:[~2004-06-21 20:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-21 19:02 can TSC tick with different speeds on SMP? "Kirill Korotaev"
2004-06-21 19:22 ` Pasi Savolainen
2004-06-21 19:32 ` Grzegorz Kulewski
2004-06-21 20:50 ` James Cleverdon [this message]
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=200406211350.09295.jamesclv@us.ibm.com \
--to=jamesclv@us.ibm.com \
--cc=kksx@mail.ru \
--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