From: Priya <pbhat@acis.ufl.edu>
To: Tim Deegan <Tim.Deegan@citrix.com>
Cc: Dan Magenheimer <dan.magenheimer@oracle.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"xen-users@lists.xensource.com" <xen-users@lists.xensource.com>
Subject: Re: [Xen-devel] Domain-Virtual time
Date: Fri, 26 Feb 2010 12:20:01 -0500 [thread overview]
Message-ID: <5c3550fe1002260920n77c43e2cmbfd6ccc29be527c9@mail.gmail.com> (raw)
In-Reply-To: <20100226170101.GV368@whitby.uk.xensource.com>
[-- Attachment #1.1: Type: text/plain, Size: 1814 bytes --]
Thanks Tim!
I have some follow-up questions:
1. How can I check/change the timer_mode on a *XenServer* HVM and on a
Xen HVM?
2. How can I check/change the time-source on my machines?
3.
>
> No; they are showing system time modified according to the timer_mode
> setting, then extrapolated into a collection of virtual timers and
> reconstituted by the linux kernel.
Can you please elaborate a little bit. Or please point me to a reference.
Thanks again !
Pr
On Fri, Feb 26, 2010 at 12:01 PM, Tim Deegan <Tim.Deegan@citrix.com> wrote:
> Hi,
>
> At 16:46 +0000 on 26 Feb (1267202798), Priya wrote:
> > The funny thing is that NTP is measuring a very different drift on my
> > three machines (-189.206, -108.373 and -71.321 parts per million). The
> > drift reported on Domain-0 is -11.393. So I don't think my machines
> > are showing the system time.
>
> No; they are showing system time modified according to the timer_mode
> setting, then extrapolated into a collection of virtual timers and
> reconstituted by the linux kernel.
>
> I don't know a lot about linux HVM because I always run Linux with PV
> kernels, but on Windows I've found that the (virtual) ACPI PM timer is a
> better time-source than the HPET or RTC.
>
> > In addition, the negative sign on the drift means that my machines are
> > running faster that the real time, which is again puzzling.
>
> Xen system time generally does drift forward, IIRC that's because xen
> always tends to catch up to the fastest CPU, so cross-CPU jitter turns
> into forward drift. Linux may be doing the same thing inside the HVM
> VM, where the jitter is higher.
>
> Tim.
>
> --
> Tim Deegan <Tim.Deegan@citrix.com>
> Principal Software Engineer, XenServer Engineering
> Citrix Systems UK Ltd. (Company #02937203, SL9 0BG)
>
>
[-- Attachment #1.2: Type: text/html, Size: 2510 bytes --]
[-- Attachment #2: Type: text/plain, Size: 137 bytes --]
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
next prev parent reply other threads:[~2010-02-26 17:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 16:03 Domain-Virtual time Priya
2010-02-25 20:36 ` [Xen-devel] " Dan Magenheimer
2010-02-26 16:46 ` Priya
2010-02-26 17:01 ` Tim Deegan
2010-02-26 17:20 ` Priya [this message]
2010-02-26 17:46 ` Dan Magenheimer
2010-02-26 18:52 ` Priya
2010-02-26 17:26 ` Dan Magenheimer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5c3550fe1002260920n77c43e2cmbfd6ccc29be527c9@mail.gmail.com \
--to=pbhat@acis.ufl.edu \
--cc=Tim.Deegan@citrix.com \
--cc=dan.magenheimer@oracle.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).