[Xen-devel] [PATCH x86_64] x86_64 doesn't tell the HV it is panicing

[Don Zickus <dzickus@xxxxxxxxxx>]

Hello,

I apologize if this patch makes it to the list twice.  Didn't realize I needed
to subscribe first. 

As the subject says, the domU kernel just sits around forever on a panic
because the HV doesn't know it crashed.  This patch sends the signal,
which allows the kernel to be cleaned up (according to whatever guest.conf
rules).  

It is basically copied and pasted from the i386 branch.  

Cheers,
Don



--- linux-2.6.15.noarch/arch/x86_64/kernel/setup-xen.c.orig     2006-03-16 
15:04:45.000000000 -0500
+++ linux-2.6.15.noarch/arch/x86_64/kernel/setup-xen.c  2006-03-16 
15:11:53.000000000 -0500
@@ -91,6 +91,11 @@ EXPORT_SYMBOL(hypercall_page);
 /* Allows setting of maximum possible memory size  */
 unsigned long xen_override_max_pfn;
 
+static int xen_panic_event(struct notifier_block *, unsigned long, void *);
+static struct notifier_block xen_panic_block = {
+       xen_panic_event, NULL, 0 /* try to go last */
+};
+
 unsigned long *phys_to_machine_mapping;
 unsigned long *pfn_to_mfn_frame_list_list, *pfn_to_mfn_frame_list[512];
 
@@ -632,6 +637,9 @@ void __init setup_arch(char **cmdline_p)
        unsigned long kernel_end;
 
 #ifdef CONFIG_XEN
+       /* Register a call for panic conditions. */
+       notifier_chain_register(&panic_notifier_list, &xen_panic_block);
+
        ROOT_DEV = MKDEV(RAMDISK_MAJOR,0); 
        kernel_end = 0;         /* dummy */
        screen_info = SCREEN_INFO;
@@ -980,6 +988,17 @@ void __init setup_arch(char **cmdline_p)
 #endif /* !CONFIG_XEN */
 }
 
+#ifdef CONFIG_XEN
+static int
+xen_panic_event(struct notifier_block *this, unsigned long event, void *ptr)
+{
+       HYPERVISOR_sched_op(SCHEDOP_shutdown, SHUTDOWN_crash);
+       /* we're never actually going to get here... */
+       return NOTIFY_DONE;
+}
+#endif /* !CONFIG_XEN */
+
+
 static int __cpuinit get_model_name(struct cpuinfo_x86 *c)
 {
        unsigned int *v;


----- End forwarded message -----

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel