From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Jan Beulich" <jbeulich@novell.com>
Subject: recursive panics
Date: Thu, 15 Nov 2007 13:37:15 +0000
Message-ID: <473C599B.76E4.0078.0@novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

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