From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: recurring boot time scalability issues affecting time management Date: Tue, 11 May 2010 11:22:22 +0100 Message-ID: References: <4BE936B002000078000023D7@vpn.id2.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4BE936B002000078000023D7@vpn.id2.novell.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: Jan Beulich , "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 11/05/2010 09:51, "Jan Beulich" wrote: >>>> Keir Fraser 11.05.10 09:57 >>> >> On 11/05/2010 07:59, "Jan Beulich" wrote: >> >>> I wonder whether the time handling code in Xen itself shouldn't/can't >>> therefore be made more robust, or at least reliably detect this sort of >>> issue (from past analysis of similar problems, the platform timer is >>> rolling over due to there not being frequent enough invocations of >>> plt_overflow()) to make analysis of the problem easier. >> >> Something like the attached? > > Yes, except that you probably mean __builtin_llabs() rather than > __builtin_abs(). xen-unstable:21346 -- Keir