WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] recursive panics

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] recursive panics
From: "Jan Beulich" <jbeulich@xxxxxxxxxx>
Date: Thu, 15 Nov 2007 13:37:15 +0000
Delivery-date: Thu, 15 Nov 2007 05:36:40 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
With crash_debug enabled, we're seeing recursive panics because of the
embedded int3 in panic(), as long as interrupts were disabled at the top
level exception's origin (in the given case, in the context switch code). It
would seem to me that even in this case, reporting back to the debugger,
if any, or ignoring the breakpoint (if there's no debugger) should be the
normal operation, but I'm somewhat hesitant to add more special case
code to entry.S. Are there any ideas how to solve this in a more elegant
way?

Thanks, Jan


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

<Prev in Thread] Current Thread [Next in Thread>