lkml.org 
[lkml]   [2002]   [Feb]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Missed jiffies
george anzinger wrote:

> "H. Peter Anvin" wrote:
>
>>Followup to: <3C6E833F.1A888B3C@mvista.com>
>>By author: george anzinger <george@mvista.com>
>>In newsgroup: linux.dev.kernel
>>
>>>One of the nasty problems, especially with machines such as yours (i.e.
>>>lap tops), is the fact that TSC is NOT clocked at a fixed rate. It is
>>>affected by throttling (reduced in 12.5% increments) and by power
>>>management.
>>>
>>If the TSC is affected by HLT, throttling, or C2 power management, the
>>TSC is broken (as it is on Cyrix chips, for example.) The TSC usually
>>*is* affected by C3 power management, but the OS should be aware of
>>C3.
>>
> Gosh I would LIKE to think this is true. Could you give a reference? I
> believe Andrew Grover thinks that what I have stated is true. If I am
> wrong, it will make the high-res-timers MUCH more acceptable as the TSC
> overhead is MUCH lower that the ACPI pm timer.
>
> Do I have this right Andrew?
>


What I have defined above is what Linux considers a "working" TSC. I
belive this to be functional on Intel, AMD and Transmeta CPUs.

However, there are some systems -- especially using older chips with less
PLL delays -- which change CLKIN on the fly.

-hpa



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:24    [W:0.046 / U:43.248 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site