From: Ashok Raj <ashok.raj@intel.com>
To: Shaohua Li <shaohua.li@intel.com>
Cc: Ashok Raj <ashok.raj@intel.com>,
Srivatsa Vaddagiri <vatsa@in.ibm.com>,
Andrew Morton <akpm@osdl.org>,
torvalds@osdl.org, linux-kernel@vger.kernel.org, bryce@osdl.org
Subject: Re: [PATCH] Check for online cpus before bringing them up
Date: Mon, 20 Mar 2006 17:25:51 -0800 [thread overview]
Message-ID: <20060320172551.A16743@unix-os.sc.intel.com> (raw)
In-Reply-To: <1142903285.11430.1.camel@sli10-desk.sh.intel.com>; from shaohua.li@intel.com on Tue, Mar 21, 2006 at 09:08:05AM +0800
On Tue, Mar 21, 2006 at 09:08:05AM +0800, Shaohua Li wrote:
> > +
> > +#ifdef CONFIG_HOTPLUG_CPU
> > + /*
> > + * We do warm boot only on cpus that had booted earlier
> > + * Otherwise cold boot is all handled from smp_boot_cpus().
> > + * cpu_callin_map is set during AP kickstart process. Its reset
> > + * when a cpu is taken offline from cpu_exit_clear().
> > + */
> > + if (!cpu_isset(cpu, cpu_callin_map))
> > + ret = __smp_prepare_cpu(cpu);
> Does this work for boot time? cpu_callin_map isn't set at boot time for
> APs.
>
Yes,
I tested on a 2 way system and it booted fine. This is set durng the kickstart process
when smp_callin() is called after AP receives boot ipi.
--
Cheers,
Ashok Raj
- Open Source Technology Center
next prev parent reply other threads:[~2006-03-21 1:26 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-16 17:44 [PATCH] Check for online cpus before bringing them up Srivatsa Vaddagiri
2006-03-17 1:08 ` Andrew Morton
2006-03-17 1:16 ` Shaohua Li
2006-03-17 8:46 ` Srivatsa Vaddagiri
2006-03-17 9:04 ` Andrew Morton
2006-03-17 14:13 ` Srivatsa Vaddagiri
2006-03-18 14:09 ` Ashok Raj
2006-03-21 1:08 ` Shaohua Li
2006-03-21 1:25 ` Ashok Raj [this message]
2006-03-21 1:36 ` Shaohua Li
2006-10-06 23:10 ` Status on CPU hotplug issues Bryce Harrington
2006-10-06 23:29 ` Andrew Morton
2006-10-07 0:00 ` Bryce Harrington
2006-10-07 10:35 ` Pavel Machek
2006-10-07 20:42 ` Bryce Harrington
2006-10-08 18:29 ` Heiko Carstens
2006-10-08 19:14 ` Pavel Machek
2006-10-11 1:08 ` [BUG] 2.6.19-rc1-mm1: fs/file.c138 on ia64 Bryce Harrington
2006-10-11 1:15 ` Andrew Morton
2006-10-11 5:38 ` Bryce Harrington
2006-10-07 10:24 ` Status on CPU hotplug issues Pavel Machek
2006-10-07 20:25 ` Bryce Harrington
2006-10-08 19:13 ` Pavel Machek
2006-10-09 7:42 ` Bryce Harrington
2006-10-07 21:57 ` Pavel Machek
2006-10-09 21:40 ` Randy Dunlap
2006-10-23 22:26 ` Bryce Harrington
2006-11-08 5:35 ` Randy Dunlap
2006-11-08 5:52 ` Bryce Harrington
2006-03-17 12:21 ` [PATCH] Check for online cpus before bringing them up Ashok Raj
2006-03-17 13:59 ` Srivatsa Vaddagiri
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=20060320172551.A16743@unix-os.sc.intel.com \
--to=ashok.raj@intel.com \
--cc=akpm@osdl.org \
--cc=bryce@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shaohua.li@intel.com \
--cc=torvalds@osdl.org \
--cc=vatsa@in.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.