From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Cc: Dan Magenheimer <dan.magenheimer@oracle.com>
Subject: Re: xen tsc problems?
Date: Tue, 13 Jul 2010 15:43:27 +0100 [thread overview]
Message-ID: <C8623A1F.1A802%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1007131433440.21432@kaball-desktop>
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
next prev parent reply other threads:[~2010-07-13 14:43 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 [this message]
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
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=C8623A1F.1A802%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=dan.magenheimer@oracle.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).