public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] add init_start_cpus to config boot cpus -v2
Date: Sun, 14 Dec 2008 01:55:56 -0800	[thread overview]
Message-ID: <20081214015556.16615d55.akpm@linux-foundation.org> (raw)
In-Reply-To: <4944B5A4.9060706@kernel.org>

On Sat, 13 Dec 2008 23:28:36 -0800 Yinghai Lu <yinghai@kernel.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?



  reply	other threads:[~2008-12-14  9:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-14  6:06 [PATCH] add command line init_start_cpus Yinghai Lu
2008-12-14  6:18 ` Andrew Morton
2008-12-14  7:28   ` [PATCH] add init_start_cpus to config boot cpus -v2 Yinghai Lu
2008-12-14  9:55     ` Andrew Morton [this message]
2008-12-15  0:11 ` [PATCH] add command line init_start_cpus Andi Kleen
2008-12-15  3:39   ` Yinghai Lu
2008-12-16 21:18     ` Ingo Molnar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20081214015556.16615d55.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=yinghai@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox