From: Khalid Aziz <khalid_aziz@hp.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Fastboot mailing list <fastboot@lists.osdl.org>,
Linux ia64 <linux-ia64@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"Luck, Tony" <tony.luck@intel.com>
Subject: Re: [PATCH] kexec for ia64
Date: Tue, 14 Mar 2006 09:00:15 -0700 [thread overview]
Message-ID: <1142352015.18421.3.camel@lyra.fc.hp.com> (raw)
In-Reply-To: <20060313224404.1133fc28.akpm@osdl.org>
On Mon, 2006-03-13 at 22:44 -0800, Andrew Morton wrote:
> Khalid Aziz <khalid_aziz@hp.com> wrote:
> > + int cpu;
> > +
> > + for_each_online_cpu(cpu) {
> > + if (cpu != smp_processor_id())
> > + cpu_down(cpu);
> > + }
> > +#else
> > + smp_call_function(kexec_stop_this_cpu, (void *)image->start, 0, 0);
> > +#endif
> > +#endif
>
> Why is different code needed for hotplug cpu?
Hi Andrew,
It is preferable to use cpu_down() to shoot down a cpu, but this
function is available only with CONFIG_HOTPLUG_CPU. If
CONFIG_HOTPLUG_CPU is not enabled, only other way to shut down slave
CPUs in a state where they would come back up when the new kernel boots
up and sends them IPI is to hold them in a fake rendezvous which is what
the function kexec_stop_this_cpu() does. So the choices are either to
keep both ways of shutting down CPUs or go with kexec_stop_this_cpu()
for all cases.
Thanks for the comments. I will move declarations to header files as you
suggested.
--
Khalid
====================================================================
Khalid Aziz Open Source and Linux Organization
(970)898-9214 Hewlett-Packard
khalid.aziz@hp.com Fort Collins, CO
"The Linux kernel is subject to relentless development"
- Alessandro Rubini
next prev parent reply other threads:[~2006-03-14 16:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-13 17:39 [PATCH] kexec for ia64 Khalid Aziz
2006-03-14 6:44 ` Andrew Morton
2006-03-14 16:00 ` Khalid Aziz [this message]
2006-03-14 6:48 ` Zou Nan hai
2006-03-14 16:08 ` Khalid Aziz
2006-03-15 0:07 ` Zou Nan hai
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=1142352015.18421.3.camel@lyra.fc.hp.com \
--to=khalid_aziz@hp.com \
--cc=akpm@osdl.org \
--cc=fastboot@lists.osdl.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.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