[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20081214015556.16615d55.akpm@linux-foundation.org>
Date: Sun, 14 Dec 2008 01:55:56 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Yinghai Lu <yinghai@...nel.org>
Cc: Ingo Molnar <mingo@...e.hu>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] add init_start_cpus to config boot cpus -v2
On Sat, 13 Dec 2008 23:28:36 -0800 Yinghai Lu <yinghai@...nel.org> wrote:
>
> Impact: new command line
>
> so could select cpus to be started during init stage.
I already knew that :(
> example:
> init_start_cpus=2,4,6
> to start core 0 only on every node or thread 0 or all cores
>
> init_start_cpus=0
> not start other APs, and later let user to use
> echo 1 > /sys/devices/cpu/cpu2
> to start them in user space.
>
But why? Why is this useful? Why did you even bother writing the
code? Who wants this? For what reason? What value has it?
This stuff matters.
> +static __initdata cpumask_var_t cpu_init_start_mask;
OK.
I also suggested that this code not be added in init/main.c. What
happened to that idea?
--
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