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] Re: [PATCH] clocksource=tsc

To: "dan.magenheimer@xxxxxxxxxx" <dan.magenheimer@xxxxxxxxxx>, "Xen-Devel (E-mail)" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: [PATCH] clocksource=tsc
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Fri, 18 Jul 2008 20:28:13 +0100
Cc: Dave Winchell <dwinchell@xxxxxxxxxxxxxxx>
Delivery-date: Fri, 18 Jul 2008 12:28:09 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20080718105135031.00000001344@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/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
Thread-index: AcjkZ5sqwfzsRK8bRLOogZ+uDOy+agBK8Gg8AAvqplAALhkLxQADB+XQAAFG8VoAATgKoAAAlQPwABMp4zAABk1eMAARsq0wAAB8cZgAR4se4AARsDekAAeSCxIAAEo1uwAGMYeAAADIYbQAAK6J0AAAaB4RAAJwCWAABuWEaQ==
Thread-topic: [Xen-devel] Re: [PATCH] clocksource=tsc
User-agent: Microsoft-Entourage/11.4.0.080122
On 18/7/08 17:51, "Dan Magenheimer" <dan.magenheimer@xxxxxxxxxx> wrote:

> I guess you are correct as long as "generate a time record"
> doesn't include recomputing the scaling factor every
> second (which is I think what introduces the jitter... see
> more on this below).
> 
> However, I'm not sure why you perceive the aesthetics to
> be so bad to put "if (ideal_clocksource)" in get_s_time()
> and a few other places in time.c... or for that matter in
> the PV guest code.

Extra special case are ugly. And then if they extend into the guests then
you also have to worry about new guests on old Xen and old guests on new Xen
(i.e., compatibility both ways). Which is not a good way to go when there is
an easy way to hide this new implementation from guests. Indeed we would
only update the TSC and system-time stamps -- the scale factor would never
change.

 -- Keir



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

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