xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Mukesh Rathor <mukesh.rathor@oracle.com>
Cc: "Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>
Subject: Re: current not very current (vs curr_vcpu)
Date: Thu, 25 Feb 2010 08:07:55 +0000	[thread overview]
Message-ID: <C7ABE05B.B497%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <20100224170618.6d7c4608@mantra.us.oracle.com>

On 25/02/2010 01:06, "Mukesh Rathor" <mukesh.rathor@oracle.com> wrote:

>> Okay, see how xen-unstable:20969 works for you.
> 
> 
> Yup, better. Thanks a lot.
> 
> BTW, since debuggers only care about BUG and ASSERT, perhaps
> DEBUGGER_trap_entry could be moved after BUGFRAME_warn, next time
> you are in do_invalid_op().

DEBUGGER_trap_entry is done early in all trap handlers. There are
DEBUGGER_trap_fatal hooks in the ASSERT and BUG paths already which can be
hooked in preference. The place to express that policy is in the debugger.h
header or the debugger itself. And I think it already is done correctly.

 -- Keir

      reply	other threads:[~2010-02-25  8:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-19  4:21 current not very current (vs curr_vcpu) Mukesh Rathor
2010-02-19  8:12 ` Keir Fraser
2010-02-19 19:23   ` Mukesh Rathor
2010-02-19 21:34     ` Keir Fraser
2010-02-20  3:50       ` Mukesh Rathor
2010-02-20  7:45         ` Keir Fraser
2010-02-22 18:59           ` Mukesh Rathor
2010-02-23 19:46           ` Mukesh Rathor
2010-02-23 21:03             ` Keir Fraser
2010-02-24  3:55               ` Mukesh Rathor
2010-02-24 10:45                 ` Keir Fraser
2010-02-25  1:06                   ` Mukesh Rathor
2010-02-25  8:07                     ` Keir Fraser [this message]

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=C7ABE05B.B497%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=Xen-devel@lists.xensource.com \
    --cc=mukesh.rathor@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).