From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: RE: xen tsc problems?
Date: Tue, 13 Jul 2010 11:06:03 -0700 (PDT) [thread overview]
Message-ID: <49010aa0-3f75-4987-ba9e-7ff5bc7e6f8d@default> (raw)
In-Reply-To: <C8626573.1A92C%keir.fraser@eu.citrix.com>
/me wonders if timer_mode=1 is the default for xl?
Or only for xm?
> -----Original Message-----
> From: Keir Fraser [mailto:keir.fraser@eu.citrix.com]
> Sent: Tuesday, July 13, 2010 11:48 AM
> To: Stefano Stabellini; Dan Magenheimer
> Cc: xen-devel@lists.xensource.com
> Subject: Re: [Xen-devel] xen tsc problems?
>
> On 13/07/2010 18:39, "Stefano Stabellini"
> <Stefano.Stabellini@eu.citrix.com>
> wrote:
>
> > I started to wonder why the guest is seeing such a big tsc warp when
> xen
> > is seeing 0, so I added more tracing and eventually I found out that
> the
> > value of v->arch.hvm_vcpu.stime_offset is significantly different
> > between the two vcpus and the difference increases after the scaling.
> > Then I added timer_mode=1 to my vm config file and the problem went
> > away.
> > I think that delay_for_missed_ticks shouldn't cause tsc scew in
> > the guest.
>
> Well, timer_mode=1 is the default and I doubt in all seriousness that
> the
> other modes get any use or testing.
>
> -- Keir
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2010-07-13 18:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-13 14:37 xen tsc problems? Stefano Stabellini
2010-07-13 14:43 ` Keir Fraser
2010-07-13 15:37 ` Dan Magenheimer
2010-07-13 17:39 ` Stefano Stabellini
2010-07-13 17:48 ` Keir Fraser
2010-07-13 18:06 ` Dan Magenheimer [this message]
2010-07-13 18:14 ` Stefano Stabellini
2010-07-13 18:59 ` Keir Fraser
2010-07-13 19:32 ` Dan Magenheimer
2010-07-13 18:12 ` Keir Fraser
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=49010aa0-3f75-4987-ba9e-7ff5bc7e6f8d@default \
--to=dan.magenheimer@oracle.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=keir.fraser@eu.citrix.com \
--cc=xen-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.