All of lore.kernel.org
 help / color / mirror / Atom feed
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: tsc_mode == 1 and hvm guests
Date: Thu, 6 May 2010 13:04:40 +0100	[thread overview]
Message-ID: <C8086EE8.13654%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1005061225520.11380@kaball-desktop>

Should Cc Dan on this, as he's the original implementer.

 K.

On 06/05/2010 12:41, "Stefano Stabellini" <Stefano.Stabellini@eu.citrix.com>
wrote:

> Hi all,
> going through the vtsc code in xen I realized that vtsc_offset and, more
> importantly, vtsc_to_ns/ns_to_vtsc are never used for hvm guests.
> That means that if tsc_mode == 1 the rdtsc values returned to pv guests
> and the ones returns to hvm guests are fundamentally different because
> in the first case they are scaled by the guest tsc frequency and in the
> second case they are not.
> The fact that noone at the moment is calling tsc_set_info with gtsc_khz
> != 0 doesn't help spotting this problem.
> 
> Is there a reason for this or is it just a bug?
> 
> Also there are two gtsc_khz AFAICT: d->arch.tsc_khz and
> d->arch.hvm_domain.gtsc_khz, why hvm guests have their own separate
> record of the guest tsc frequency, when they never actually change it?
> 
> BTW I noticed these problems because they prevent the pvclock algorithm
> from working correctly in a PV on HVM linux guest.
> 
> Thanks,
> 
> Stefano
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

  reply	other threads:[~2010-05-06 12:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-06 11:41 tsc_mode == 1 and hvm guests Stefano Stabellini
2010-05-06 12:04 ` Keir Fraser [this message]
2010-05-06 15:03   ` Dan Magenheimer
2010-05-07  8:18     ` Zhang, Xiantao
2010-05-07 19:06       ` Stefano Stabellini
2010-05-07 19:35         ` Dan Magenheimer
2010-05-10 12:41           ` Stefano Stabellini
2010-05-10 12:42             ` Keir Fraser
2010-05-10 12:58               ` Stefano Stabellini
2010-05-10 14:47               ` Dan Magenheimer
2010-05-10 14:55                 ` Stefano Stabellini
2010-05-10 15:01                   ` Dan Magenheimer
2010-05-10 15:19                     ` Stefano Stabellini
2010-05-10 15:30                       ` Dan Magenheimer
2010-05-10 16:36                         ` Stefano Stabellini
2010-05-09 14:04         ` Zhang, Xiantao
2010-05-10 12:48           ` Stefano Stabellini

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=C8086EE8.13654%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 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.