* Andrew Morton <akpm@linux-foundation.org> wrote:

quoted text
> On Tue, 29 Jul 2008 23:31:05 +0100
> Russell King - ARM Linux <linux@arm.linux.org.uk> wrote:
> 
> > But then some bright spark thought it would be a good idea to get
> > rid of printk_clock().
> 
> <does git-log, searches for printk_clock>

i think this is a fresh regression via the introduction of 
kernel/sched_clock.c. We lost the (known) early-init behavior of 
cpu_clock() in the !UNSTABLE_SCHED_CLOCK case. The fix would be to 
restore that, not to reintroduce printk_clock().

Peter, any ideas?

	Ingo
--
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/