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

Re: [Xen-devel] [PATCH 0/2] Improve hpet accuracy

To: "dan.magenheimer@xxxxxxxxxx" <dan.magenheimer@xxxxxxxxxx>, Dave Winchell <dwinchell@xxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 0/2] Improve hpet accuracy
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Mon, 09 Jun 2008 22:18:33 +0100
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Ben Guthro <bguthro@xxxxxxxxxxxxxxx>
Delivery-date: Mon, 09 Jun 2008 14:18:13 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20080609144837187.00000002776@djm-pc>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcjIFBNOSTfhtJHySxCkafUaaZcKSgBjZoBVAAHlHtAABTaSTAARWR2JABqYZAAAAh8/sA==
Thread-topic: [Xen-devel] [PATCH 0/2] Improve hpet accuracy
User-agent: Microsoft-Entourage/11.4.0.080122
On 9/6/08 21:48, "Dan Magenheimer" <dan.magenheimer@xxxxxxxxxx> wrote:

>> At guest install time you ought to be able to tell whether the guest
>> will use hpet or not based on its version (RHELx, SLESy, Winz etc etc)
>> and decide whether missed-ticks accounting is required or not.
> 
> Unfortunately this is not true on Linux, at least without gathering
> (and hardcoding) more information about the system.  Whether hpet is
> used or not is dependent not only on the OS/version and hvm config
> parameters, but also on kernel command line parameters and even
> the underlying CPU.  For example, on RHEL5u1, if the tsc is synchronized
> and the CPU is Intel, and no kernel parameters are chosen, tsc will be
> chosen as the default clocksource even if hpet is present.  Ugly.

It's not immediately obvious that adding further independent configuration
knobs to twiddle would make our lives that much easier. However it certainly
increases the test matrix.

In your example above, by synchronised TSC do you mean constant-rate TSC?
That can at least be hidden in CPUID now.

 -- Keir



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