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] Add a timer mode that disables pending missed ti

To: Dave Winchell <dwinchell@xxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Add a timer mode that disables pending missed ticks
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Fri, 02 Nov 2007 09:40:37 +0000
Cc: "Dong, Eddie" <eddie.dong@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, "Shan, Haitao" <haitao.shan@xxxxxxxxx>, "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>
Delivery-date: Fri, 02 Nov 2007 02:41:27 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <472A41CA.7080405@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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcgdNGwmqpqhxoknEdyrMQAX8io7RQ==
Thread-topic: [Xen-devel] [PATCH] Add a timer mode that disables pending missed ticks
User-agent: Microsoft-Entourage/11.3.6.070618
On 1/11/07 21:14, "Dave Winchell" <dwinchell@xxxxxxxxxxxxxxx> wrote:

> 1. Increase missed ticks threshold to 100 seconds. Per the comment in
> the patch,

I assume that's the magic number 100000 in the patch? I think removing the
check entirely would be better than an arbitrarily high threshold that we're
baiscally hoping will never trigger.

> 3.  Call pt_process_missed_ticks() unconditionally and place the
>     test for no_missed_tick_accounting inside pt_process_missed_ticks().
>     This returns the calculation for the next timer expiration
>     to the original method. The original method is important
>     as it sets up a theoretical time space at t=0 where expirations
>     occur only at n*period, where n is any integer. This, in turn, removes
>     rounding errors.

Why do 'rounding errors' matter? I thought that no_missed_tick_accounting
was for guests which sampled the TSC on tick interrupt and used that to
determine elapsed wall time, in which case why would it matter when exactly
the tick interrupt is delivered?

 -- Keir



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