Re: Fwd: [GIT PULL] timer changes for v3.10

[Ingo Molnar]

* Feng Tang <feng.tang@xxxxxxxxx> wrote:

> > is even worse than that. Machine can stay is s2ram for weeks (for a 
> > lot more if it is desktop and you do s2ram for powersaving). Also 
> > temperature of CPU varies a lot between active and s2ram states. Is 
> > TSC good enough?
> 
> Yes, I think it is relatively precise. Per our test, system time backed 
> by the S3 non stop TSC only has 1 second drift after 4 days running 
> (with mixed running and S3 states). And before using this feature, we've 
> seen many time drift problems due to the RTC HW or system FW with our 
> platforms.

Nice result ...

Is that with NTP running?

Without NTP, the TSC fast-calibration on bootup is not (expected to be) 
nearly as precise as the 1:345600 precision you've measured.

Thanks,

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