From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: RADclock on Xen (was Re: [PATCH] time-xen : Reset
	monotonic time when sync up time from dom0 to domU)
Date: Fri, 15 Oct 2010 16:21:05 -0700
Message-ID: <4CB8E1E1.6080906@goop.org>
References: <9C56B6AEEB2D60488B29B880DF7E53BE03C1B2C6B6@SSDEXCH2.websense.com>
	<4CB4672E020000780001C752@vpn.id2.novell.com>
	<0b6cc1b3-f838-482e-89dc-6f19cc8c47cc@default>
	<20101013161657.GJ4007@whitby.uk.xensource.com>
	<4CB5E2C3.9010500@goop.org>
	<20101014090737.GK4007@whitby.uk.xensource.com>
	<4CB793CE.50907@goop.org>
	<20101015083937.GM4007@whitby.uk.xensource.com>
	<5869AFE5-6E86-46D8-8817-98DCAF39F7FC@unimelb.edu.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <5869AFE5-6E86-46D8-8817-98DCAF39F7FC@unimelb.edu.au>
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: Darryl Veitch <dveitch@unimelb.edu.au>
Cc: Dan Magenheimer <dan.magenheimer@oracle.com>, xen-devel@lists.xensource.com, Keir Fraser <keir@xen.org>, Tim Deegan <Tim.Deegan@citrix.com>, Shunli Yi <syi@websense.com>, Jan Beulich <JBeulich@novell.com>, Saipu Liu <saliu@websense.com>, Hang Du <hdu@websense.com>, Timothy Broomhead <tim@unixtech.com.au>, Julien Ridoux <jridoux@unimelb.edu.au>
List-Id: xen-devel@lists.xenproject.org

 On 10/15/2010 05:10 AM, Darryl Veitch wrote:
> Hi Tim,
>
> good to hear from you.  Dom0 will need the usual RADclock patches
> which now integrate the Xen support. These supply two main things:  
> i)  kernel level raw timestamping (ie reading of the chosen counter)
> of packet arrivals and departures in `good but safe' locations and an
> ability to pass those timestamps up (works transparently with pcap,
> and doesn't affect its normal operation)

Are you trying to get these changes into mainline Linux?

> ii)  the ability to access the raw counter of choice from both kernel
> and user context

The kernel already has this info, and I have patches for mapping it into
userspace.  Or would a syscall suffice?

> In the Xen context, the choice of counter will end up being Xen
> Clocksource which is already accessible to guests as is already a
> suitable counter of the right size (64-bit).
>
> Take a look at the RADclock downloads
> <http://www.cubinlab.ee.unimelb.edu.au/radclock/download.php> page.
> There have been a number of changes recently in particular in the
> integration of the Xen support so I will direct you to Julien Ridoux
> for finer-grained answers as he and Tim Broomhead actually wrote the
> code. 
>
> We'll be quizzing you shortly about our needs to make this work under
> HV using that way to access the Xenstore you mentioned, and we'd like
> to talk to you about how to improve packet timestamping under Dom0. 

OK.

    J