From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: kexec: offline non panic CPUs on Kdump panic
Date: Fri, 26 Jul 2013 11:49:08 +0100 [thread overview]
Message-ID: <20130726104908.GC17886@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <1374817287-27952-1-git-send-email-vijay.kilari@gmail.com>
[Adding Stephen Warren since he has been working in this area]
On Fri, Jul 26, 2013 at 06:41:27AM +0100, vijay.kilari at gmail.com wrote:
> From: Vijaya Kumar K <Vijaya.Kumar@caviumnetworks.com>
>
> In case of normal kexec kernel load, all cpu's are offlined
> before calling machine_kexec() under kernel_kexec() function.
> But in case crash panic cpus are relaxed in
> machine_crash_nonpanic_core() SMP function but not offlined.
>
> When crash kernel is loaded with kexec and on panic trigger
> machine_kexec() checks for number of cpus online.
> If more than one cpu is online machine_kexec() fails to load
> with below error
>
> kexec: error: multiple CPUs still online
>
> In machine_crash_nonpanic_core() SMP function, offline CPU
> before cpu_relax
>
> Signed-off-by: Vijaya Kumar K <Vijaya.Kumar@caviumnetworks.com>
> ---
> arch/arm/kernel/machine_kexec.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm/kernel/machine_kexec.c b/arch/arm/kernel/machine_kexec.c
> index 4fb074c..163b160 100644
> --- a/arch/arm/kernel/machine_kexec.c
> +++ b/arch/arm/kernel/machine_kexec.c
> @@ -73,6 +73,7 @@ void machine_crash_nonpanic_core(void *unused)
> crash_save_cpu(®s, smp_processor_id());
> flush_cache_all();
>
> + set_cpu_online(smp_processor_id(), false);
> atomic_dec(&waiting_for_crash_ipi);
> while (1)
> cpu_relax();
Ok, I guess this will work since the new kernel is loaded somewhere higher
in memory and the crashed kernel will stick around, so the non-crashing CPUs
can sit around spinning.
Will
next prev parent reply other threads:[~2013-07-26 10:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 5:41 [PATCH] ARM: kexec: offline non panic CPUs on Kdump panic vijay.kilari at gmail.com
2013-07-26 10:49 ` Will Deacon [this message]
2013-07-26 17:08 ` Stephen Warren
2013-07-26 17:11 ` Will Deacon
2013-07-30 10:37 ` Vijay Kilari
2013-07-30 16:59 ` Stephen Warren
2013-07-31 11:37 ` Vijay Kilari
2013-07-31 17:14 ` Stephen Warren
2013-08-01 13:49 ` Vijay Kilari
2013-08-01 16:25 ` Stephen Warren
2013-08-12 12:18 ` Vijay Kilari
2013-08-13 11:18 ` Will Deacon
2013-07-26 17:05 ` Stephen Warren
2013-07-30 10:05 ` Vijay Kilari
2013-07-30 16:57 ` Stephen Warren
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=20130726104908.GC17886@mudshark.cambridge.arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).