Re: [PATCH] sched: Support current clocksource handling in fallbacksched_clock().
From: Thomas Gleixner
Date: Thu May 28 2009 - 13:02:06 EST
On Thu, 28 May 2009, Daniel Walker wrote:
> > > > Do any module based clocksources even exist right now?
> > > > clocksource_unregister only seems to be used 3 times..
> > >
> > > Good point, it appears its not even exported.
> > >
> > > Thomas mentioned modules, I assumed.
> > >
> > The drivers/clocksource/ drivers in theory could be modular anyways.
> > Handling this transition properly is at least one less barrier to modular
> > clocksources, so I think it's progress regardless. I don't remember what
> > all of the other issues were though, John probably remembers.
> I don't think it's an important case to consider right now ..
> clocksources are usually so integral to the system putting one in a
> module seems counterintuitive.
That does not matter at all. If we have an unregister call then we
have to be prepared for
- the memory which contained the clocksource is freed
- the underlying hardware is going away.
It does not matter at all if that happens in a compiled in or in a
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/