]> xenbits.xensource.com Git - xen.git/commitdiff
[IA64] panic_domain should only crash the domain
authorawilliam@xenbuild.aw <awilliam@xenbuild.aw>
Thu, 13 Apr 2006 20:44:39 +0000 (14:44 -0600)
committerawilliam@xenbuild.aw <awilliam@xenbuild.aw>
Thu, 13 Apr 2006 20:44:39 +0000 (14:44 -0600)
Don't crash Xen in case of panic_domain.  Simply crash the domain.

Signed-off-by: Tristan Gingold <tristan.gingold@bull.net>
xen/arch/ia64/xen/xenmisc.c

index 239ae441e2232129393cecad83d19f5e89a6edf3..915ec038cc07f43a4e7dd5c51f7d229c4907b5b6 100644 (file)
@@ -346,11 +346,7 @@ void panic_domain(struct pt_regs *regs, const char *fmt, ...)
        va_list args;
        char buf[128];
        struct vcpu *v = current;
-//     static volatile int test = 1;   // so can continue easily in debug
-//     extern spinlock_t console_lock;
-//     unsigned long flags;
     
-loop:
        printf("$$$$$ PANIC in domain %d (k6=0x%lx): ",
                v->domain->domain_id, 
                __get_cpu_var(cpu_kr)._kr[IA64_KR_CURRENT]);
@@ -364,16 +360,7 @@ loop:
        } else {
                debugger_trap_immediate();
        }
-       domain_pause_by_systemcontroller(current->domain);
-       v->domain->shutdown_code = SHUTDOWN_crash;
-       set_bit(_DOMF_shutdown, &v->domain->domain_flags);
-       if (v->domain->domain_id == 0) {
-               int i = 1000000000L;
-               // if domain0 crashes, just periodically print out panic
-               // message to make post-mortem easier
-               while(i--);
-               goto loop;
-       }
+       domain_crash_synchronous ();
 }
 
 /* FIXME: for the forseeable future, all cpu's that enable VTi have split