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: RADclock on Xen (was Re: [Xen-devel] [PATCH] time-xen : Reset monoto

To: Darryl Veitch <dveitch@xxxxxxxxxxxxxx>
Subject: Re: RADclock on Xen (was Re: [Xen-devel] [PATCH] time-xen : Reset monotonic time when sync up time from dom0 to domU)
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Thu, 21 Oct 2010 13:49:09 -0700
Cc: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Keir Fraser <keir@xxxxxxx>, Tim Deegan <Tim.Deegan@xxxxxxxxxx>, Shunli Yi <syi@xxxxxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxxxx>, Saipu Liu <saliu@xxxxxxxxxxxx>, Hang Du <hdu@xxxxxxxxxxxx>, Timothy Broomhead <tim@xxxxxxxxxxxxxxx>, Julien Ridoux <jridoux@xxxxxxxxxxxxxx>
Delivery-date: Thu, 21 Oct 2010 13:50:19 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <63C6DF1D-933B-47CA-8FDF-9E15095740DE@xxxxxxxxxxxxxx>
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: <9C56B6AEEB2D60488B29B880DF7E53BE03C1B2C6B6@xxxxxxxxxxxxxxxxxxxxx> <4CB4672E020000780001C752@xxxxxxxxxxxxxxxxxx> <0b6cc1b3-f838-482e-89dc-6f19cc8c47cc@default> <20101013161657.GJ4007@xxxxxxxxxxxxxxxxxxxxxxx> <4CB5E2C3.9010500@xxxxxxxx> <20101014090737.GK4007@xxxxxxxxxxxxxxxxxxxxxxx> <4CB793CE.50907@xxxxxxxx> <20101015083937.GM4007@xxxxxxxxxxxxxxxxxxxxxxx> <5869AFE5-6E86-46D8-8817-98DCAF39F7FC@xxxxxxxxxxxxxx> <4CB8E1E1.6080906@xxxxxxxx> <63C6DF1D-933B-47CA-8FDF-9E15095740DE@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.9) Gecko/20100921 Fedora/3.1.4-1.fc13 Lightning/1.0b3pre Thunderbird/3.1.4
 On 10/20/2010 08:36 PM, Darryl Veitch wrote:
>
> On 16/10/2010, at 10:21 AM, Jeremy Fitzhardinge wrote:
>
>> 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?
>
> We are intending to do this, but have not pushed comprehensively yet,
> though we hope to start soon after we have the adoption into FreeBSD
> finalised (theoretically around end-2010).  We have had some
> discussions with John Stultz in preparation.   Would you be interested
> in being involved in encouraging adoption here ? :-) 

I'm happy to give you help out where I can.  John is definitely a person
who should be involved.  Where's the current set of patches?

>
>>
>>> 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?
>
> We use syscall's currently.

OK, that's simple.   What do you add?  A new lock time for clock_gettime?

    J

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

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