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/
Home Products Support Community News


RE: [Xen-devel] TSC virtualization across different host frequency platf

To: "Dong, Eddie" <eddie.dong@xxxxxxxxx>, Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] TSC virtualization across different host frequency platform migration
From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
Date: Thu, 23 Apr 2009 11:20:33 +0800
Accept-language: en-US
Acceptlanguage: en-US
Cc: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, "Zhang, Xiantao" <xiantao.zhang@xxxxxxxxx>
Delivery-date: Wed, 22 Apr 2009 20:23:22 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <9832F13BD22FB94A829F798DA4A8280501A7FC09FD@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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>
References: <9832F13BD22FB94A829F798DA4A8280501A7D29D36@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <a8eca533-4045-4802-a856-40800278d9ff@default> <9832F13BD22FB94A829F798DA4A8280501A7FC09FD@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcnDZfIIPGB/X3zJRA2gCz9ONiocoQAS8nVwAAQFdTA=
Thread-topic: [Xen-devel] TSC virtualization across different host frequency platform migration
>From: Dong, Eddie 
>Sent: 2009年4月23日 9:29
>Dan Magenheimer wrote:
>> Hi Eddie/Kevin --
>> I'm sorry to be dense, but I don't understand the
>> details of your solution.  I'm also not sure I
>> understand the problem you are trying to solve.
>> The problem description doesn't describe a problem,
>> just an event.
>> I'm guessing the problem is:  When a guest chooses
>> TSC as its primary clocksource AND a migration later
>> occurs to a host with a different TSC frequency
>> THEN wallclock time (e.g. the "date" command)
>> becomes incorrect.
>Mostly yes though don't know if guest wall clock depends on 
>TSC heavily.
>> I'm also guessing that you are NOT trying to solve
>> the problem:  An application that uses TSC
>> heavily to measure the passage of time AND
>> calibrates TSC on host A AND invisibly
>> migrates to host B with a different TSC
>> frequency THEN will NOT be able to accurately
>> measure the passage of time.  However, it will
>> continue to be monotonically increasing.
>Yes, if we don't scale the TSC.
>The proposal tries to solve the problem.
>We can use software trap and emulate to scale the TSC so
>that guest TSC after migration is same with that before migration.
>But this is not optimial since the overhead may be too high. So we 
>propose to use smart scaling, which continuously use TSC_OFFSET,
>but adjust the TSC_OFFSET value time to time (today it is fixed), 
>so that an application that uses TSC heavily to measure the 
>passage of time
>can get correct time.

So we're really not trying to solve the micro-level accuracy if app
tries to use TSC for that purpose, which always bias from bare
metal as long as running in a VM. Here we're trying to ensure
macro-level accuracy and thus ToD in guest after migration, with 
performance optimized if app in VM uses gettimeofday frequently. 
In that way, gap between trap vs. notrap would be orders of 

Xen-devel mailing list