Messages in this thread | | | Subject | Re: [PATCH] Re: x86_32 tsc/pit and hrtimers | From | Alok Kataria <> | Date | Thu, 09 Oct 2008 16:22:55 -0700 |
| |
On Thu, 2008-10-09 at 15:50 -0700, Chris Snook wrote: > Alok Kataria wrote: > > On Thu, 2008-10-09 at 14:03 -0700, Chris Snook wrote: > > > > I agree that in general this should be no, but since this is a > > commandline variable it will be normally set for only those systems > > which have only TSC as a option or know that the TSC is reliable. > > wouldn't doing this be ok for such systems ? > > Hardware doesn't deliberately do any TSC synchronization, though you might get > it by accident in some configurations. A VMware guest gets it for free thanks > to the hypervisor doing it in software, but we need to run the check when we're > booting on bare metal.
The TSC sync algorithm right now expects that TSC are perfectly in sync between cpus. But, the hardware doesn't deliberately do any synchronization, so we can have situations where TSC was (accidently ? )off by a marginal value during boot and as a result we mark TSC as unstable and don't use it as a clocksource at all. For systems like the ones Jeff is using wouldn't that be a problem. IOW, even though the TSC was *marginally* off during bootup it should still be used as a clocksource, since you have no other option, no ?
> Jeff's patch enables the feature with as little risk as > possible. TSC sync is pretty cheap, so it's not worth it to add a more > dangerous special case just for guests of certain hypervisors.
I am not saying that we should go ahead and disable TSC sync for all cases, we can very well do that just when running on a particular type of system. The point here is to understand what should we do in a case like above, on physical hardware.
Thanks, Alok
> -- Chris
| |