xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>,
	Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
	xen-devel@lists.xensource.com
Subject: RE: xen tsc problems?
Date: Tue, 13 Jul 2010 08:37:41 -0700 (PDT)	[thread overview]
Message-ID: <8a9d6a6f-4727-4211-979d-5cf7ec2eade6@default> (raw)
In-Reply-To: <C8623A1F.1A802%keir.fraser@eu.citrix.com>

> From: Keir Fraser [mailto:keir.fraser@eu.citrix.com]
> 
> On 13/07/2010 15:37, "Stefano Stabellini"
> <Stefano.Stabellini@eu.citrix.com>
> wrote:
> 
> > Does this mean that the host has some serious tsc issues?
> > Can this be a symptom of a bug in xen?
> > Suggestion are welcome.
> 
> The 's' and 't' debug key handlers will be useful to get an idea of how
> stable host TSCs are.
> 
>  -- Keir

Also you can try max_cstate=0 as a Xen boot parameter to rule
out power management screwing up the tsc.

> > Does this mean that the host has some serious tsc issues?

Probably.  But the default tsc_mode (0) is intended to hide all
such issues.  Could you check the 's' debug-key output to
ensure your guest is actually running with tsc_mode=0?

> > Can this be a symptom of a bug in xen?

Well, if the guest has problems with the default tsc_mode (0),
which does complete tsc emulation, I suppose it could be
a bug in Xen.  In particular, I wonder if the code that
recovers from deep C-states (and writes to the TSC) is broken.
IIRC, there was some changesets in that area recently.
If the problem goes away with max_cstate=0, that would be
a good place to start.

Dan

  reply	other threads:[~2010-07-13 15:37 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 [this message]
2010-07-13 17:39     ` Stefano Stabellini
2010-07-13 17:48       ` Keir Fraser
2010-07-13 18:06         ` Dan Magenheimer
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=8a9d6a6f-4727-4211-979d-5cf7ec2eade6@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 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).