From mboxrd@z Thu Jan  1 00:00:00 1970
From: Chris Lalancette <clalance@redhat.com>
Subject: Re: vgettimeofday disabled?
Date: Wed, 03 Sep 2008 18:02:06 +0200
Message-ID: <48BEB4FE.3000900@redhat.com>
References: <C4E4734D.26B55%keir.fraser@eu.citrix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <C4E4734D.26B55%keir.fraser@eu.citrix.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

Keir Fraser wrote:
> We probably don't update vxtime structure, so you likely get dodgy results
> from do_vgettimedofday(). However, forcing vxtime to track vcpu0's time info
> obtained from Xen would probably be quite easy to do and may be accurate
> enough.
> 
> But, without that extra engineering, I recommend you check what answers
> you're getting from gettimeofday(). Could be quite a significant
> performance/correctness tradeoff ;-)

Ah, OK.  So there's not really a fundamental issue (which I was worried about),
more just it hasn't been implemented all the way.  Interestingly, it doesn't
seem to be explicitly disabled in the LKML pv_ops implementation, so either it's
being updated properly there, or time is *way* off.

Thanks for the info.

Chris Lalancette