WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Clocksources and other mysteries

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Clocksources and other mysteries
From: Carsten Schiers <carsten@xxxxxxxxxx>
Date: Mon, 12 Jan 2009 10:43:25 +0100
Delivery-date: Mon, 12 Jan 2009 01:44:09 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
First of all: we are still speaking about am AMD 4050e on MSI M56S-S3 board and
Xen 3.2-1 as well as 2.6.18-xen-3.1-2-amd64 kernel.

I set cpufreq=dom9-kernel and cpuidle. When I use cpufreq-set or if the govenor
is set to cpufreq_ondemand, every frequency change is generating log messages 
that time went backwards. I already understood that this is related to state
changes (both p-state and c-state), nevertheless, I don't understand whether
this messages are indicating a problem. Messages appear in both: dom0 and domus.

My system has a 25 MHz HPET, as xm demsg reports. But in Dom0, jiffies is the
only available (and used) clocksource. In 64 bit domus, it's also only jiffies,
in 32 Bit domus, there is also tsc and pit available, but always jiffies used.

First mystery: when jiffies is used as clocksource, why is the system checking
and complaining about deltas in TSC? Can I thus ignore them?

Second mystery: when Xen reports:(XEN) Platform timer is 25.000MHz HPET, why
isn't Xen using it? Shouldn't it? Wouldn't be the HPET the best choice for my
non-TSC-invariant CPU?

Sorry, if this is not the right place to get better knowledge of Xen 
internals...

Best Regards,
Carsten.

____________________________________________________________________
Carsten Schiers, Henseweg 23h, 22359 Hamburg, Tel. (040) 6044 9717, 
carsten@xxxxxxxxxx

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>