From: Keir Fraser Subject: Re: Time goes backwards in dom0 in xen-unstable Date: Wed, 15 Apr 2009 08:30:37 +0100 Message-ID: References: <2bd706d8-59aa-440f-b38c-ad63523d3eab@default> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <2bd706d8-59aa-440f-b38c-ad63523d3eab@default> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Dan Magenheimer , "Xen-Devel (E-mail)" List-Id: xen-devel@lists.xenproject.org On 14/04/2009 20:36, "Dan Magenheimer" wrote: > I'm seeing some "Time went backwards" errors reported > in dom0 in near-tip (c/s 19515) xen-unstable build. > It's rare and random and not reproducible, but here's > the report that just showed up. There was no load > running at the time. > > I can move to 3.4-rc1 if that would be helpful but I > don't remember seeing any time-related changes recently. > > This was on my dual-core test machine which reports > lots of power management info during Xen boot. If you specify 'cpuidle=off' as a Xen boot parameter, does that make the timer_interrupt scalability problem go away, and this time backwards problem? I was going to enable by default in 3.4 but could go the other way. -- Keir