From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marco Tizzoni Subject: Re: [Xen-devel] Re: About profiling xen Date: Wed, 30 Sep 2009 11:06:25 +0200 Message-ID: References: <196324.1267.qm@web94604.mail.in2.yahoo.com> <20090930063747.GG1434@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-users-bounces@lists.xensource.com Errors-To: xen-users-bounces@lists.xensource.com To: =?ISO-8859-1?Q?Pasi_K=E4rkk=E4inen?= Cc: "Fajar A." , Fasiha Ashraf , xen , xen-users@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Enabling debug on kernel I realized the problem is related to timer accuracy. ------------------------------------------------------------------------ hal9k-dom0 ~ # cat /proc/timer_list Timer List Version: v0.3 HRTIMER_MAX_CLOCK_BASES: 2 now at 784689453083 nsecs cpu: 0 clock 0: .index: 0 .resolution: 999848 nsecs [........] hal9k-dom0 ~ # cat /sys/devices/system/clocksource/clocksource0/available_clocksource xen jiffies hal9k-dom0 ~ # cat /sys/devices/system/clocksource/clocksource0/current_clocksource xen ------------------------------------------------------------------------ Is there a way to make available a better timer (hpet,acpi....)? Also, on another xen box (rhel 5.2), I've a 'pit' clocksource in available_clocksource. After: # sysctl -w xen.independent_wallclock=1 and ------------------------------------------------------------------------------------------------------------------------------------ # echo pit > /sys/devices/system/clocksource/clocksource0/current_clocksource [root@station1 init.d]# cat /sys/devices/system/clocksource/clocksource0/current_clocksource jiffies ------------------------------------------------------------------------------------------------------------------------------------ the clocksource is unmodified. m-