[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[XenPPC] Re: [Xen-devel] [Patch] [RFC] avoid debugger_trap when we don't expect

Hi, Keir

>This doesn't need to be fixed on x86 -- the int3 handler will return
>silently if the debugger is not configured. It would be nice if the ia64
>handler would do the same. If that is not possible then change only ia64
>code and if you need to be able to probe gdbstub configuration then add a
>public function to do that rather than grope at internal state. The same
>goes for powerpc, *if* it is broken in the first place.
I know the int3 hanlder return well on x86 if it is not configured.
But the route may be not safe. The debugger_trap is called after hypervisor
panic and dom0 panic. So I want to avoid the needless route for kexec/kdump.

Best Regards,

Akio Takebe

Xen-ppc-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.