From: Jay Lan <jlan@engr.sgi.com>
To: linux-ia64@vger.kernel.org
Subject: [PATCH]send slave cpus to SAL slave loop on crash (IA64)
Date: Mon, 30 Oct 2006 20:36:13 +0000 [thread overview]
Message-ID: <4546623D.5000105@engr.sgi.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 319 bytes --]
This patch is to fix a problem of interrupts being sent to cpus
that can not respond.
This patch would return slave cpus to SAL slave loop, at time of
crash, except cpu0. The cpu0 is a special case as there is no way
to return it to SAL, so cpu0 is better handled in firmware.
Signed-off-by: Jay Lan <jlan@sgi.com>
[-- Attachment #2: send-cpus-to-slave-loop --]
[-- Type: text/plain, Size: 898 bytes --]
Index: linux/arch/ia64/kernel/crash.c
===================================================================
--- linux.orig/arch/ia64/kernel/crash.c 2006-10-17 17:09:45.662734380 -0700
+++ linux/arch/ia64/kernel/crash.c 2006-10-30 12:27:12.080526026 -0800
@@ -146,14 +146,21 @@ machine_kdump_on_init(void)
void
kdump_cpu_freeze(struct unw_frame_info *info, void *arg)
{
+ int cpuid = smp_processor_id();
+
local_irq_disable();
crash_save_this_cpu();
current->thread.ksp = (__u64)info->sw - 16;
atomic_inc(&kdump_cpu_freezed);
- kdump_status[smp_processor_id()] = 1;
+ kdump_status[cpuid] = 1;
mb();
- for (;;)
- cpu_relax();
+ /* return cpus (except cpu0) to SAL slave loop */
+ if (cpuid == 0) {
+ for (;;)
+ cpu_relax();
+ } else {
+ ia64_jump_to_sal(&sal_boot_rendez_state[cpuid]);
+ }
}
static int
next reply other threads:[~2006-10-30 20:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-30 20:36 Jay Lan [this message]
2006-10-31 2:02 ` [PATCH]send slave cpus to SAL slave loop on crash (IA64) Zou, Nanhai
2006-10-31 4:33 ` Zou, Nanhai
2006-10-31 8:59 ` Jay Lan
2006-10-31 9:11 ` Zou, Nanhai
2006-10-31 18:08 ` Jay Lan
2006-11-03 17:42 ` Jay Lan
2006-11-08 2:01 ` Zou, Nanhai
2006-11-10 19:23 ` Jay Lan
2006-11-14 1:25 ` Zou, Nanhai
2006-11-20 23:13 ` Zou Nan hai
2006-11-20 23:33 ` Jay Lan
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=4546623D.5000105@engr.sgi.com \
--to=jlan@engr.sgi.com \
--cc=linux-ia64@vger.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