Re: [patch 13/19] GTOD: Mark TSC unusable for highres timers

[Pavel Machek]

Hi!

> > > > If so, could that function use the PIT/pmtimer/etc for working out 
> > > > if the TSC is bust, rather than directly using jiffies?
> > > 
> > > there's no realiable way to figure out the TSC is bust: some CPUs 
> > > have a slight 'skew' between cores for example. On some systems the 
> > > TSC might skew between sockets. A CPU might break its TSC only once 
> > > some
> > 
> > But we could still do a whitelist?
> 
> we could, but it would have to be almost empty right now :-) Reason: 

Well, if it would contain at least 50% of the UP machines... that
would be reasonably long list for a start.
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
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/