On Fri, 2007-06-01 at 09:11 -0700, Daniel Walker wrote:
quoted text > On Fri, 2007-06-01 at 17:52 +0200, Peter Zijlstra wrote:
quoted text > > The whole issue is that you don't have any control over what clocksource
> > you'll end up with. If it so happens that pmtimer gets selected your
> > whole box will crawl if its used liberaly, like the patch under
> > discussion does.
>
> You can have control over it, which I think the whole point of this
> discussion ..
No you don't, clocksource will gladly discard the TSC when its not found
stable enough (the majority of the systems today). While it would be
good enough for sched_clock().
-
unsubscribe notice 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/
Messages in current thread:
Re: [PATCH 3/5] lockstat: core infrastructure , Peter Zijlstra , (Fri Jun 1, 11:43 am)