From: Shaohua Li <shaohua.li@intel.com>
To: Ashok Raj <ashok.raj@intel.com>
Cc: 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: Tue, 21 Mar 2006 09:08:05 +0800 [thread overview]
Message-ID: <1142903285.11430.1.camel@sli10-desk.sh.intel.com> (raw)
In-Reply-To: <20060318060958.A31112@unix-os.sc.intel.com>
On Sat, 2006-03-18 at 06:09 -0800, Ashok Raj wrote:
> On Fri, Mar 17, 2006 at 07:43:22PM +0530, Srivatsa Vaddagiri wrote:
> > On Fri, Mar 17, 2006 at 01:04:12AM -0800, Andrew Morton wrote:
> > > OK.. I guess we should fix those architectures while we're thinking about it.
> >
> > Only x86 has this bug, so only x86 needs to be fixed. Neverthless
> > Ashok's patch [1] should address all architectures that may implement
> > smp_prepare_cpu() in future as well.
> >
> Hi Vatsa
>
> Since smp_prepare_cpu was introduced only to work around warm-boot on i386 due to the
> strange kickstart process of AP's. I have moved this al-together within __cpu_up()
> i386 arch code, so its less confusing to other arch's that have done it right already.
>
> Here is the updated patch, it removes smp_prepare_cpu() from being called from generic
> core cpuhotplug code, and moved it to i386 side.
>
> I did some basic up/down testing on a 2 way PIII box.
>
> Shaohua, could you take a look at this code, and also check suspend/resume is not
> affected?
>
> Andrew, could we queue it to -mm for some exposure before inclusion.
>
> thanks
>
> --
> Cheers,
> Ashok Raj
> - Open Source Technology Center
>
>
> Check if cpu can be onlined before calling smp_prepare_cpu()
>
> - Moved check for online cpu out of smp_prepare_cpu()
> - Moved default declaration of smp_prepare_cpu() to kernel/cpu.c
> - Removed lock_cpu_hotplug() from smp_prepare_cpu() to around it, since
> its called from cpu_up() as well now.
> - Removed clearing from cpu_present_map during cpu_offline as it breaks using cpu_up()
> directly during a subsequent online operation.
>
> Signed-off-by: Ashok Raj <ashok.raj@intel.com>
> --------------------------------------------------------
> arch/i386/kernel/smpboot.c | 21 +++++++++++++++++----
> drivers/base/cpu.c | 9 +--------
> include/linux/cpu.h | 1 -
> kernel/power/smp.c | 4 +---
> 4 files changed, 19 insertions(+), 16 deletions(-)
>
> Index: linux-2.6.16-rc6-mm1/arch/i386/kernel/smpboot.c
> ===================================================================
> --- linux-2.6.16-rc6-mm1.orig/arch/i386/kernel/smpboot.c
> +++ linux-2.6.16-rc6-mm1/arch/i386/kernel/smpboot.c
> @@ -1002,7 +1002,6 @@ void cpu_exit_clear(void)
>
> cpu_clear(cpu, cpu_callout_map);
> cpu_clear(cpu, cpu_callin_map);
> - cpu_clear(cpu, cpu_present_map);
>
> cpu_clear(cpu, smp_commenced_mask);
> unmap_cpu_to_logical_apicid(cpu);
> @@ -1021,14 +1020,13 @@ static void __devinit do_warm_boot_cpu(v
> complete(info->complete);
> }
>
> -int __devinit smp_prepare_cpu(int cpu)
> +static int __devinit __smp_prepare_cpu(int cpu)
> {
> DECLARE_COMPLETION(done);
> struct warm_boot_cpu_info info;
> struct work_struct task;
> int apicid, ret;
>
> - lock_cpu_hotplug();
> apicid = x86_cpu_to_apicid[cpu];
> if (apicid == BAD_APICID) {
> ret = -ENODEV;
> @@ -1053,7 +1051,6 @@ int __devinit smp_prepare_cpu(int cpu)
> zap_low_mappings();
> ret = 0;
> exit:
> - unlock_cpu_hotplug();
> return ret;
> }
> #endif
> @@ -1379,6 +1376,22 @@ void __cpu_die(unsigned int cpu)
>
> int __devinit __cpu_up(unsigned int cpu)
> {
> + int ret=0;
> +
> +#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.
Thanks,
Shaohua
next prev parent reply other threads:[~2006-03-21 1:12 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-16 17:44 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 [this message]
2006-03-21 1:25 ` Ashok Raj
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=1142903285.11430.1.camel@sli10-desk.sh.intel.com \
--to=shaohua.li@intel.com \
--cc=akpm@osdl.org \
--cc=ashok.raj@intel.com \
--cc=bryce@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®