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] Xen timing mode

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Xen timing mode
From: Priya <pbhat@xxxxxxxxxxxx>
Date: Tue, 23 Feb 2010 12:33:19 -0500
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 23 Feb 2010 09:34:08 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type; bh=nY0S39dWVm0WP8CiKNXLTXUzBgsfo+TYqoUblzDXwcY=; b=wYxSZXx/s/21HYQRvt/+avk1Kh3otIlXkQy9UiPMfdayWsS0gYdS0AjwMbfk/00tUo FigLwSmPoRCP4D9ShePJuIZ3nv7CTeOI4fbcgDvGTTqS1VuLmk7IqPTdfQLwPifSvBCF bSuImJ/aJtz+StlNkuHn/LpA3FNrC8Xwkcwaw=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=pELL0X9hF/s6VAHKGBUTlYNvcc/YrPjKIBEn9Dp1LRYdNRZ1ouMN4qwt2jXlzl5vQP W3RQQp8F4Ws7pPnE0emD/KpyUUR4DpX+ypbGn9UkzGIUbX1S2FmESN+UkAoUY+JVRqos RK2JdyGDmZlua6aNnZaxO4PVowHDRmNFsuC8g=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <5c3550fe1002230929r37d1bd73mdd82fc84ee51d0fd@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: <5c3550fe1002230912j1a5d0650oa1e355652c8e3062@xxxxxxxxxxxxxx> <C7A9BE50.B018%keir.fraser@xxxxxxxxxxxxx> <5c3550fe1002230929r37d1bd73mdd82fc84ee51d0fd@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
The latest interface manual which contains a similar definition of domain-virtual time as stated in my last email can be found here:

http://www.cl.cam.ac.uk/research/srg/netos/xen/readmes/interface/interface.html#SECTION00340000000000000000

Priya

On Tue, Feb 23, 2010 at 12:29 PM, Priya <pbhat@xxxxxxxxxxxx> wrote:
The Xen Interface manual for Xen v2.0 (attached) Page 4 defines Domain - virtual time as

" The time that progresses at the same pace as system time, but only while a domain is executing -- it stops while a domain is de-scheduled. Therefore the share of the CPU that a domain receives is indicated by the rate at which its virtual time increases."

I am interesting in finding out if any of the timing system calls/instructions like gettimeofday(), hwclock(), rdtsc() can read this domain virtual time.

Thanks, again !

PS: I could not find a similar documentation for Xen v3.0 or later



On Tue, Feb 23, 2010 at 12:18 PM, Keir Fraser <keir.fraser@xxxxxxxxxxxxx> wrote:
What do you mean by domain - virtual time?


On 23/02/2010 17:12, "Priya" <pbhat@xxxxxxxxxxxx> wrote:

> Thanks !
>
> In that case, how does a para-virtualized user domain find the domain -
> virtual time ?
>
> --Priya
>
> On Tue, Feb 23, 2010 at 12:08 PM, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
> wrote:
>> Independent_wallclock is specific to Linux PV guests, and is set within the
>> guest. Timer_mode is specific to HVM guests and is a domain build-time
>> config option.
>>
>>  -- Keir
>>
>> On 23/02/2010 16:50, "PBhat" <pbhat@xxxxxxxxxxxx> wrote:
>>
>>>
>>> A question about timing modes in Xen came up after reading the documentation
>>> on
>>> http://wiki.xensource.com/xenwiki/XenConfigurationFileOptions?highlight=(int
>>> er
>>> <http://wiki.xensource.com/xenwiki/XenConfigurationFileOptions?highlight=%28
>>> inter>
>>> rupts)|(timer)
>>> configuration file options  and I was wondering if you could help me with
>>> it.
>>>
>>>     * I know that Xen has a facility on the user domains to change the
>>> timing from something called the ' http://openskill.info/infobox.php?ID=1451
>>> independent wallclock ' to 'dependent clock' and vice versa. The way to do
>>> this is to toggle the parameter /proc/sys/xen/independent_wallclock between
>>> 0 (dependent) and 1 (independent)
>>>
>>>
>>>     * Now, the documentation on the configuration options for xen virtual
>>> machine under the heading of Timers contains no mention of the above
>>> mentioned facility, but instead talks about something called a 'timer_mode'
>>>
>>>
>>>  timer_mode: Timer mode (0=delay virtual time when ticks are missed;
>>> 1=virtual time is always wallclock time
>>>       timer_mode (default=1; Value='TIMER_MODE')
>>>
>>> Now my question is whether the timer mode  = 1 is equivalent to independent_
>>> wallclock?
>>>
>>> I think the answer is no. While timer_mode = 1 decides whether the virtual
>>> machine is able to read the Domain-0 time, the independent_wallclock decides
>>> whether you need NTP sychronization on both (user and control) domains or
>>> not.
>>>
>>> Namely, in the timer_mode = 1, the gettimeofday() called from the virtual
>>> machine will return the domain virtual time, but time_mode = 0
>>> gettimeofday() instruction from the virtual machine will return the system
>>> time.
>>>
>>> The independent and dependent modes have an effect on whether the virtual
>>> machines can use the NTP or any other synchronization of Domain-0.
>>>
>>> Is my understanding correct?
>>>
>>> I further want to know whether the working remains similar on Xen HVMs also.
>>> In the sense that are Hardware based virtual machines capable of reading the
>>> Domain-0 system time in an analogous way?
>>>
>>>
>>> Your help would be much appreciated. I am new to this area and I apologize
>>> if my questions seem too basic.
>>
>>
>>
>
>





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