xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: kevin.tian@intel.com, jbeulich@suse.com, eddie.dong@intel.com,
	xen-devel@lists.xen.org, jun.nakajima@intel.com,
	suravee.suthikulpanit@amd.com
Subject: Re: [PATCH v4 2/3] x86/svn: Enable TSC scaling
Date: Wed, 16 Apr 2014 11:53:56 +0100	[thread overview]
Message-ID: <534E6144.1010709@citrix.com> (raw)
In-Reply-To: <1397611668-15338-3-git-send-email-boris.ostrovsky@oracle.com>

On 16/04/14 02:27, Boris Ostrovsky wrote:
> TSC ratio enabling logic is inverted: we want to use it when we
> are running in native tsc mode, i.e. when d->arch.vtsc is zero.
>
> Also, since now svm_set_tsc_offset()'s calculations depend
> on vtsc's value, we need to call hvm_funcs.set_tsc_offset() after
> vtsc changes in tsc_set_info().
>
> In addition, with TSC ratio enabled, svm_set_tsc_offset() will
> need to do rdtsc. With that we may end up having TSCs on guest's
> processors out of sync. d->arch.hvm_domain.sync_tsc which is set
> by the boot processor can now be used by APs as reference TSC
> value instead of host's current TSC.
>
> Signed-off-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>

"svm" in the subject?

~Andrew

> ---
>  xen/arch/x86/hvm/hvm.c           |   15 ++++++++++-----
>  xen/arch/x86/hvm/svm/svm.c       |   15 +++++++++------
>  xen/arch/x86/hvm/vmx/vmx.c       |    2 +-
>  xen/arch/x86/hvm/vmx/vvmx.c      |    4 ++--
>  xen/arch/x86/hvm/vpt.c           |   16 ++++++++++------
>  xen/arch/x86/time.c              |   29 +++++++++++++++++++++++++++--
>  xen/include/asm-x86/hvm/domain.h |    6 ++++++
>  xen/include/asm-x86/hvm/hvm.h    |    8 +++++---
>  xen/include/asm-x86/msr.h        |    6 +++---
>  xen/include/xen/time.h           |    1 +
>  10 files changed, 74 insertions(+), 28 deletions(-)
>
>

  parent reply	other threads:[~2014-04-16 10:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-16  1:27 [PATCH v4 0/3] Time-related fixes for migration Boris Ostrovsky
2014-04-16  1:27 ` [PATCH v4 1/3] x86: Use native RDTSC(P) execution when guest and host frequencies are the same Boris Ostrovsky
2014-04-16  9:54   ` Jan Beulich
2014-04-16 13:02     ` Boris Ostrovsky
2014-04-16 11:38   ` Jan Beulich
2014-04-16 14:28     ` Boris Ostrovsky
2014-04-16 14:37       ` Jan Beulich
2014-04-16 15:33         ` Boris Ostrovsky
2014-04-16 16:15           ` Jan Beulich
2014-04-16 16:44             ` Boris Ostrovsky
2014-04-17  6:29               ` Jan Beulich
2014-04-16  1:27 ` [PATCH v4 2/3] x86/svn: Enable TSC scaling Boris Ostrovsky
2014-04-16 10:21   ` Jan Beulich
2014-04-16 10:53   ` Andrew Cooper [this message]
2014-04-16  1:27 ` [PATCH v4 3/3] x86/HVM: Use fixed TSC value when saving or restoring domain Boris Ostrovsky
2014-04-16 10:22   ` Jan Beulich

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=534E6144.1010709@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=eddie.dong@intel.com \
    --cc=jbeulich@suse.com \
    --cc=jun.nakajima@intel.com \
    --cc=kevin.tian@intel.com \
    --cc=suravee.suthikulpanit@amd.com \
    --cc=xen-devel@lists.xen.org \
    /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).