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

Re: [Xen-devel] recursive panics

To: Jan Beulich <jbeulich@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] recursive panics
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Thu, 15 Nov 2007 14:33:24 +0000
Delivery-date: Thu, 15 Nov 2007 06:34:21 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <473C599B.76E4.0078.0@xxxxxxxxxx>
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
Thread-index: AcgnlHpEuQ3APpOHEdywhgAX8io7RQ==
Thread-topic: [Xen-devel] recursive panics
User-agent: Microsoft-Entourage/11.3.6.070618
I don't think this has been the case since Xen 3.0.4. In newer Xen, the
entry.S asm code happily passes through exceptions with interrupts disabled.

 -- Keir

On 15/11/07 13:37, "Jan Beulich" <jbeulich@xxxxxxxxxx> wrote:

> 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



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

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