From: george anzinger <george@mvista.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Fionn Behrens <fionn@unix-ag.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: System time warping around real time problem - please help
Date: Tue, 25 Mar 2003 18:28:37 -0800 [thread overview]
Message-ID: <3E811055.5040202@mvista.com> (raw)
In-Reply-To: <1048637613.29944.17.camel@irongate.swansea.linux.org.uk>
Alan Cox wrote:
> On Tue, 2003-03-25 at 22:55, Fionn Behrens wrote:
>
>>>This all sounds very much like the TSCs are drifting WRT each other.
>>>Is it possible that you have some power management code (or hardware)
>>>that is slowing one cpu and not the other?
>>
>>Well, I still don't really know what TSCs actually are (or what TSC
>>stands for).
Stands for Time Stamp Counter. It is a special cpu register that
basically counts cpu cycles. Some times (incorrectly me thinks) it is
affected by power management code which slows the cpu by changing the
cpu frequency.
>>
>>The only suspect in that case would be the amd76x_pm.o kernel module
>>which I am admittedly using. It saves about 90Watts of power when the
>>machine is idle...
>
>
> If you are using amd76x_pm boot with "notsc", ditto for that matter
> on dual athlons with APM or ACPI in some cases. In fact I wish people
> would stop using the tsc for clock timing altogether. It simply doesn't
> work on a lot of modern systems
>
I agree, however, what is really needed is not available in x86
machines, i.e. a cpu register that has a fixed and stable count rate.
An I/O register is second best because of the long time it takes to
read it.
>
>
--
George Anzinger george@mvista.com
High-res-timers: http://sourceforge.net/projects/high-res-timers/
Preemption patch: http://www.kernel.org/pub/linux/kernel/people/rml
next prev parent reply other threads:[~2003-03-26 2:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-25 16:32 System time warping around real time problem - please help Fionn Behrens
2003-03-25 17:07 ` Richard B. Johnson
2003-03-25 17:17 ` Tim Schmielau
2003-03-25 18:12 ` Fionn Behrens
2003-03-25 18:29 ` Richard B. Johnson
2003-03-25 21:16 ` Fionn Behrens
2003-03-25 22:14 ` george anzinger
2003-03-25 22:55 ` Fionn Behrens
2003-03-26 0:13 ` Alan Cox
2003-03-26 2:28 ` george anzinger [this message]
2003-03-26 14:38 ` Alan Cox
2003-03-26 16:12 ` george anzinger
2003-03-26 17:06 ` Richard B. Johnson
2003-03-26 18:12 ` george anzinger
2003-03-26 3:11 ` Chris Friesen
2003-03-26 14:35 ` Alan Cox
2003-03-26 10:48 ` Fionn Behrens
[not found] <20030325164014$031c@gated-at.bofh.it>
2003-03-26 9:31 ` Kay Diederichs
-- strict thread matches above, loose matches on Subject: below --
2003-04-03 13:22 Fionn Behrens
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=3E811055.5040202@mvista.com \
--to=george@mvista.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=fionn@unix-ag.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.