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] Fix hvm guest time to be more accurate

To: "Dave Winchell" <dwinchell@xxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] [PATCH] Fix hvm guest time to be more accurate
From: "Dong, Eddie" <eddie.dong@xxxxxxxxx>
Date: Mon, 29 Oct 2007 17:58:37 +0800
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Ben Guthro <bguthro@xxxxxxxxxxxxxxx>
Delivery-date: Mon, 29 Oct 2007 02:59:35 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <47222F89.5070808@xxxxxxxxxxxxxxx>
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>
References: <471FB5FA.6060507@xxxxxxxxxxxxxxx> <10EA09EFD8728347A513008B6B0DA77A024823DF@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <4720ABF2.3080505@xxxxxxxxxxxxxxx> <10EA09EFD8728347A513008B6B0DA77A02482AB6@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <4721F203.6000302@xxxxxxxxxxxxxxx> <47222F89.5070808@xxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcgX/EVxkd8pJALlQ4CHP6bSMUEqvgCFelOA
Thread-topic: [Xen-devel] [PATCH] Fix hvm guest time to be more accurate
Dave Winchell wrote:
> Eddie,
> 
> I implemented #2B and ran a three hour test
> with sles9-64 and rh4u4-64 guests. Each guest had 8 vcpus
> and the box was Intel with 2 physical processors.
> The guests were running large loads.
> Clock was pit. This is my usual test setup, except that I just
> as often used AMD nodes with more processors.
> 
> The time error was .02%, good enough for ntpd.
> 
> The implementation keeps a constant guest tsc offset.
> There is no pending_nr cancellation.
> When the vpt.c timer expires, it only increments pending_nr
> if its value is zero.
> Missed_ticks() is still calculated, but only to update the new
> timeout value. There is no adjustment to the tsc offset
> (set_guest_time()) 
> at clock interrupt delivery time nor at re-scheduling time.
> 
> So, I like this method better than the pending_nr subtract.
> I'm going to work on this some more and, if all goes well,
> propose a new code submission soon.
> I'll put some kind of policy switch in too, which we can discuss
> and modify, but it will be along the lines of what we discussed below.
> 
> Thanks for your input!
> 
> -Dave
> 


Haitao Shai may posted his patch, can u check if there are something
missed?
thx,eddie

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