Re: [Xen-devel] current not very current (vs curr_vcpu)

[Mukesh Rathor <mukesh.rathor@xxxxxxxxxx>]

On Wed, 24 Feb 2010 10:45:36 +0000
Keir Fraser <keir.fraser@xxxxxxxxxxxxx> wrote:

> On 24/02/2010 03:55, "Mukesh Rathor" <mukesh.rathor@xxxxxxxxxx> wrote:
.... 
> > Well, I'm afraid not. It breaks the debug code to debug the hang.
> > More importantly, it also breaks my debuggers, which some people
> > from outside oracle are also using. Most of our new high end
> > servers are accessed via virtual serial port, so if ns16550_poll()
> > call is related to it, then it'll only get worse. Moreover, anybody
> > reading and copying that code to do something similar will be
> > misled.
> 
> 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().

Mukesh

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