Add the i386 specific crash_stop code.  This contains routines that are
called from the common crash_stop code and from the i386 notify_die
chain.

Note 1: Not tested on visw nor voyager, no hardware.

Note 2: It is missing the code to handle a notify_chain (see scenario 4
        in kernel/crash_stop.c in a later patch).  I want to make sure
        that the API design is right before adding that code.

---
 arch/i386/kernel/Makefile     |    1 
 arch/i386/kernel/crash_stop.c |   75 ++++++++++++++++++++++++++++++++++++++++++
 2 files changed, 76 insertions(+)

Index: linux/arch/i386/kernel/Makefile
===================================================================
--- linux.orig/arch/i386/kernel/Makefile
+++ linux/arch/i386/kernel/Makefile
@@ -39,6 +39,7 @@ obj-$(CONFIG_VM86)            += vm86.o
 obj-$(CONFIG_EARLY_PRINTK)     += early_printk.o
 obj-$(CONFIG_HPET_TIMER)       += hpet.o
 obj-$(CONFIG_K8_NB)            += k8.o
+obj-$(CONFIG_CRASH_STOP_SUPPORTED)     += crash_stop.o
 
 EXTRA_AFLAGS   := -traditional
 
Index: linux/arch/i386/kernel/crash_stop.c
===================================================================
--- /dev/null
+++ linux/arch/i386/kernel/crash_stop.c
@@ -0,0 +1,75 @@
+/*
+ * linux/arch/i386/crash_stop.c
+ *
+ * Copyright (C) 2006 Keith Owens <[EMAIL PROTECTED]>
+ *
+ * Most of the i386 specific bits of the crash_stop code.  There is a little
+ * bit of crash_stop code in arch/i386/kernel/{smp,smpboot}.c to handle
+ * CRASH_STOP_VECTOR, everything else is in this file.
+ */
+
+#include <linux/crash_stop.h>
+#include <linux/init.h>
+#include <linux/kernel.h>
+#include <linux/ptrace.h>
+#include <asm/kdebug.h>
+
+/* The starting point for a backtrace on a running process is set to
+ * cs_arch_cpu().  It would be nice to go up a couple of levels to start the
+ * backtrace where crash_stop() or cs_ipi() were invoked, but that is more work
+ * than I am willing to do in this function.  Starting the backtrace at
+ * cs_arch_cpu() is simple and reliable, which is exactly what we want when the
+ * machine is already failing.
+ */
+void
+cs_arch_cpu(int monarch, struct crash_stop_running_process *r)
+{
+       r->arch.esp = current_stack_pointer;
+       r->arch.eip = (unsigned long)current_text_addr();
+       /* separate any stack changes from current_stack_pointer above */
+       barrier();
+       cs_common_cpu(monarch);
+}
+
+/* Pick up any NMI IPIs that were sent by crash_stop. */
+static int
+crash_stop_arch_notify(struct notifier_block *self,
+                      unsigned long val, void *data)
+{
+       struct die_args *args = (struct die_args *)data;
+       switch(val) {
+       case DIE_NMI_IPI:
+               if (crash_stop_sent_nmi()) {
+                       crash_stop_cpu(0, args->regs);
+                       return NOTIFY_STOP;
+               }
+               break;
+       }
+       return NOTIFY_OK;
+}
+
+static struct notifier_block crash_stop_arch_nb = {
+       .notifier_call = crash_stop_arch_notify,
+       .priority = ~0 >> 1,
+};
+
+static int __init
+crash_stop_arch_init(void)
+{
+       int err = register_die_notifier(&crash_stop_arch_nb);
+       if (err) {
+               printk(KERN_ERR "Failed to register crash_stop_arch_nb\n");
+               return err;
+       }
+       return 0;
+}
+
+static void __exit
+crash_stop_arch_exit(void)
+{
+       unregister_die_notifier(&crash_stop_arch_nb);
+       return;
+}
+
+module_init(crash_stop_arch_init);
+module_exit(crash_stop_arch_exit);

-
To unsubscribe from this list: send the line "unsubscribe linux-arch" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to