Messages in this thread | | | Date | Fri, 5 Jul 2013 08:43:11 -0700 | From | Sören Brinkmann <> | Subject | Re: [PATCH] clocksource/cadence_ttc: Reuse clocksource as sched_clock |
| |
On Fri, Jul 05, 2013 at 08:30:47AM +0200, Thomas Gleixner wrote: > On Wed, 3 Jul 2013, Soren Brinkmann wrote: > > > Reuse the TTC clocksource timer as sched clock, too. Since only a single > > sched clock is supported in Linux, this feature optional and can be > > selected through Kconfig. > > This changelog doesn't make sense. > > There can be only one active sched_clock, but that does no mean, that > you cannot have different implementations compiled in. > > So if you disable this config which sched_clock is your kernel using? Jiffies
> And if you enable it, how is guaranteed that you end up with the ttc > sched_clock as the active one? Just due to initcall ordering? I assumed so. Is there a different mechanism?
Sören
-- 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/
| |