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] current not very current (vs curr_vcpu)

To: Mukesh Rathor <mukesh.rathor@xxxxxxxxxx>
Subject: Re: [Xen-devel] current not very current (vs curr_vcpu)
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Wed, 24 Feb 2010 10:45:36 +0000
Cc: "Xen-devel@xxxxxxxxxxxxxxxxxxx" <Xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 24 Feb 2010 02:49:26 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20100223195506.0e260a58@xxxxxxxxxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acq1BTKCBRhL1GpxS5C/sJ3vi4DQHwAOUyvb
Thread-topic: [Xen-devel] current not very current (vs curr_vcpu)
User-agent: Microsoft-Entourage/12.23.0.091001
On 24/02/2010 03:55, "Mukesh Rathor" <mukesh.rathor@xxxxxxxxxx> wrote:

>> Given the only thing this apparently affected was some of your own
>> ad-hoc debug code, do we really care about this at all? We can
>> probably happily just leave it.
> 
> 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.

 -- Keir



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