From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: current not very current (vs curr_vcpu) Date: Wed, 24 Feb 2010 10:45:36 +0000 Message-ID: References: <20100223195506.0e260a58@mantra.us.oracle.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20100223195506.0e260a58@mantra.us.oracle.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Mukesh Rathor Cc: "Xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 24/02/2010 03:55, "Mukesh Rathor" 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