Messages in this thread | | | Date | Thu, 31 Jul 2008 23:37:41 +0200 | From | Ingo Molnar <> | Subject | Re: Fwd: Commit 76a2a6ee8a0660a29127f05989ac59ae1ce865fa breaks PXA270 (at least)? |
| |
* Andrew Morton <akpm@linux-foundation.org> wrote:
> 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
| |