[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1160319234.5686.12.camel@localhost.localdomain>
Date: Sun, 08 Oct 2006 16:53:54 +0200
From: Thomas Gleixner <tglx@...utronix.de>
To: Daniel Walker <dwalker@...sta.com>
Cc: akpm@...l.org, johnstul@...ibm.com, mingo@...e.hu,
zippel@...ux-m68k.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: + clocksource-increase-initcall-priority.patch added to -mm
tree
On Sun, 2006-10-08 at 07:50 -0700, Daniel Walker wrote:
> On Sun, 2006-10-08 at 12:19 +0200, Thomas Gleixner wrote:
> > On Sun, 2006-10-08 at 10:06 +0200, Thomas Gleixner wrote:
> > > On Fri, 2006-10-06 at 18:53 -0700, akpm@...l.org wrote:
> > > > Since it's likely that this interface would get used during bootup I moved all
> > > > the clocksource registration into the postcore initcall. This also eliminated
> > > > some clocksource shuffling during bootup.
> > >
> > > We had the init call in postcore already. John moved it to module init
> > > to eliminate trouble with unsynced / unstable TSCs, IIRC.
> > >
> > > John, can you please comment on this.
> >
> > It also breaks pmtimer.
>
> OGAWA reported this already. It breaks the case when there is a verified
> read needed, instead of the fast read. I'll fix it.
I'd like to know, why we need to move that and you did not explain _why_
it is likely that it is used during bootup.
tglx
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists