Messages in this thread |  | | | Date | Wed, 13 Feb 2008 05:03:40 -0800 (PST) | | Subject | Re: Strange hang on ia64 with CONFIG_PRINTK_TIME=y | | From | David Miller <> | |
From: Ingo Molnar <mingo@elte.hu>
Date: Wed, 13 Feb 2008 13:57:25 +0100
> so .. how about the patch below? Note that we already had an "early
> bootup" special (the rq->idle check), it's now just made explicit via
> the scheduler_running flag.
I don't see what the problem is.
It is legal to access per-cpu data as early as you like,
it just evaluates to the static copy in the per-cpu section
of the kernel image until the per-cpu areas are setup.
rq->idle should also be zero this early as well, that's
also legal to rely upon
I see nothing illegal in what cpu_clock() is doing, that's
why I fixed the sparc64 per-cpu problem I ran into since
sparc64 was doing the wrong thing when booted on a non-zero
cpu.
|  |