xen/arm: traps: Don't panic when receiving an unknown debug trap

Even if debug trap are only meant for debugging purpose, it is quite
harsh to crash Xen if one of the trap sent by the guest is not handled.

So switch from a panic() to a printk().

Signed-off-by: Julien Grall <jgrall@amazon.com>
Reviewed-by: Stefano Stabellini <sstabellini@kernel.org>
This commit is contained in:
Julien Grall authored and Stefano Stabellini committed 2020-11-05 18:00:10 -08:00
1 parent e006b2e3be
commit 957708c2d1
1 file changed
+1 -1
+1 -1
View File
@@ -1410,7 +1410,7 @@ static void do_debug_trap(struct cpu_user_regs *regs, unsigned int code)
show_execution_state(regs);
break;
default:
panic("DOM%d: Unhandled debug trap %#x\n", domid, code);
printk("DOM%d: Unhandled debug trap %#x\n", domid, code);
break;
}
}
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.