On Thu, 5 Nov 2020, Julien Grall wrote:
> From: Julien Grall <jgr...@amazon.com>
>
> 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 <jgr...@amazon.com>
Reviewed-by: Stefano Stabellini <sstabell...@kernel.org>
> ---
> xen/arch/arm/traps.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/xen/arch/arm/traps.c b/xen/arch/arm/traps.c
> index 8f40d0e0b6b1..a36f145e6739 100644
> --- a/xen/arch/arm/traps.c
> +++ b/xen/arch/arm/traps.c
> @@ -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;
> }
> }
> --
> 2.17.1
>
