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>
Cc: xen-devel@lists.xensource.com
Subject: RE: xen tsc problems?
Date: Tue, 13 Jul 2010 12:32:27 -0700 (PDT)	[thread overview]
Message-ID: <756423e2-fa59-4f9e-bc17-e0d6ff575197@default> (raw)
In-Reply-To: <C862761F.1A95B%keir.fraser@eu.citrix.com>

> From: Keir Fraser [mailto:keir.fraser@eu.citrix.com]
> Sent: Tuesday, July 13, 2010 12:59 PM
> To: Stefano Stabellini; Dan Magenheimer
> Cc: xen-devel@lists.xensource.com
> Subject: Re: [Xen-devel] xen tsc problems?
> 
> On 13/07/2010 19:14, "Stefano Stabellini"
> <Stefano.Stabellini@eu.citrix.com>
> wrote:
> 
> > On Tue, 13 Jul 2010, Dan Magenheimer wrote:
> >> /me wonders if timer_mode=1 is the default for xl?
> >> Or only for xm?
> >
> > no, it is not.
> > Xl defaults to 0, I am going to change it right now.
> 
> Possibly we should make timer_mode=1 the default in Xen as well, and
> actually disallow setting it to 0. Clearly no good comes of it.

IIRC from >2 years ago, timer_mode=0 was best for older HVM 32-bit
Linux guests.  Obviously if the code (interacting with the tsc code)
has bit-rotted, "best" is a relative term. :-)

Dan

  reply	other threads:[~2010-07-13 19:32 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
2010-07-13 18:14           ` Stefano Stabellini
2010-07-13 18:59             ` Keir Fraser
2010-07-13 19:32               ` Dan Magenheimer [this message]
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=756423e2-fa59-4f9e-bc17-e0d6ff575197@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).