On Thu, Jul 12, 2007 at 12:50:19AM +0200, Thomas Gleixner wrote:
> Linus,
>
> On Wed, 2007-07-11 at 15:20 -0700, Linus Torvalds wrote:
> > For example, we can make sure that the code in question that actually
> > touches the hardware stays exactly the same, and then just move the
> > interfaces around - and basically guarantee that _zero_ hardware-specific
> > issues pop up when you switch over, for example.
> >
> > That way there is a gradual change-over.
>
> Ok, I can try to split this down further.
>
> > The other approach (which would be nice _too_) is to actually try to
> > convert one clock source at a time. Why is that not an option?
>
> We need to give control to the clock events core code once we convert
> one clock event device. Having two competing subsystems controlling
> different devices (e.g. PIT and APIC) is not really desirable.
Can't you take the entire legacy clock system and wrap it as a single
legacy clock source? Then you take bits out of the old system and put
them as independent sources in the new system? When the legacy clock
system is empty, you remove the legacy clock source.
--
Mathematics is the supreme nostalgia of our time.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
