From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: A clocksource question Date: Wed, 17 Mar 2010 09:20:41 -0700 Message-ID: <4BA10159.2000505@goop.org> References: <4B962748.90609@invisiblethingslab.com> <4B9BE7C0.2070401@goop.org> <4B9F1EC8.4020300@invisiblethingslab.com> <201003171435.45858.tobias.geiger@vido.info> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <201003171435.45858.tobias.geiger@vido.info> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Tobias Geiger Cc: xen-devel@lists.xensource.com, Joanna Rutkowska List-Id: xen-devel@lists.xenproject.org On 03/17/2010 06:35 AM, Tobias Geiger wrote: > i also compiled 2.6.32.9 from xen/stable , but so far i can't see much > improvement. > I'm not certain you got the relevent changeset; the "xen/stable" branch now has it, but I think I only updated it yesterday. xen/stable is now 2.6.32.10. > Still many small hiccups in Dom0 > One time (i think after HVM DomU creation) i get: > "hrtimer: interrupt took 4045137 ns" in Dom0 dmesg > That's only 4ms. Not great, but not too bad. > I also upgraded to newest xen-unstable: > xen_changeset : Wed Mar 17 09:18:34 2010 +0000 21041:066c3eead6ec > > > Could it be that the missing HPET is causing all this trouble? I just noticed > that in "xm dmesg" : > > (XEN) CPUIDLE: disabled due to no HPET. Force enable with \047cpuidle\047. > > I don't bother really about CPUIDLE, but i should perhaps about HPET ? > Is there a reason xen doesn't enable HPET? Motherboard is Intel DX58SO > I don't think that will be relevent. J