sched: make early bootup sched_clock() use safer
authorIngo Molnar <mingo@elte.hu>
Wed, 13 Feb 2008 13:02:36 +0000 (14:02 +0100)
committerIngo Molnar <mingo@elte.hu>
Mon, 25 Feb 2008 15:34:16 +0000 (16:34 +0100)
do not call sched_clock() too early. Not only might rq->idle
not be set up - but pure per-cpu data might not be accessible
either.

this solves an ia64 early bootup hang with CONFIG_PRINTK_TIME=y.

Tested-by: Tony Luck <tony.luck@gmail.com>
Acked-by: Tony Luck <tony.luck@gmail.com>
Acked-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Ingo Molnar <mingo@elte.hu>

No differences found