Re: 2.6.14-rt21: slow-running clock

[john stultz <johnstul@us.ibm.com>]

On Wed, 2005-12-14 at 11:52 +1030, Jonathan Woithe wrote:
> Hi John
> 
> > On Fri, 2005-12-09 at 12:49 +1030, Jonathan Woithe wrote:
> > > > Ok, I went digging further and found the c3tsc selection is correct on
> > > > your hardware. I'm just too used to my own laptop where the TSC varies
> > > > with cpu speed and we lower the rating value. So that should be ok.
> > > 
> > > Ok, good.  That leaves the c3tsc slowdown as the only outstanding issue at
> > > this stage.
> > > 
> > > > I'm now working on why we mis-compensate the c3tsc clocksource in the
> > > > -RT tree. 
> > > 
> > > No problem.  Let me know when you have something to test or need further
> > > info.
> > 
> > 	Attached is a test patch to see if it doesn't resolve the issue for
> > you. I get a maximum change in drift of 30ppm when idling between C3
> > states by being more careful with the C3 TSC compensation and I also
> > force timekeeping updates when cpufreq events occur. 
> 
> Unfortunately there's still an issue.

Ah, drat. 

I'm just going to dump the c3tsc clocksource for now. If C3 mode is
available, the ACPI PM timer is available (since it is used for C3
timing), so we'll just fall back to ACPI PM if we see the cpu entering
C3 mode.

I'm working to respin a new release tonight, hopefully that will make it
upstream to -rt soon and that should take care of it. Later I can look
at reworking the c3tsc clocksource, but for now things need to just
work.

Thanks again for the testing and feedback, I really appreciate your
help!
-john

-
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/