All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <jbeulich@novell.com>
To: xen-devel@lists.xensource.com
Subject: recursive panics
Date: Thu, 15 Nov 2007 13:37:15 +0000	[thread overview]
Message-ID: <473C599B.76E4.0078.0@novell.com> (raw)

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

             reply	other threads:[~2007-11-15 13:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-15 13:37 Jan Beulich [this message]
2007-11-15 14:33 ` recursive panics Keir Fraser

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=473C599B.76E4.0078.0@novell.com \
    --to=jbeulich@novell.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.