All of lore.kernel.org
 help / color / mirror / Atom feed
From: Qin Li <qin.l.li@oracle.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: xen-devel@lists.xensource.com, Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: Could you please answer some questions regarding Solaris PVHVM pvclock support.
Date: Fri, 28 Feb 2014 11:27:00 +0800	[thread overview]
Message-ID: <53100204.1050801@oracle.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1402271253000.31489@kaball.uk.xensource.com>


于 2014/2/27 21:03, Stefano Stabellini 写道:
>> >I guest linux guest will do the same thing, rdtsc() fetch current timestamp from current running vCPU, TSC out-of-sync issue is still there.
>> >It seems to me pvclock finally fix the time drift issue just because the workaround enforced as above, right?
> First you should know that TSC is not always guaranteed to be
> synchronized across multiple processors, especially on older systems.
> On "TSC-safe" systems, Xen would export a consistent TSC to guests, by
> setting the vtsc offset and scale appropriately.
Stefano,

Is there a easy way to check whether the system is "TSC-safe"? Do you 
mean "X86_FEATURE_TSC_RELIABLE" bit in "boot_cpu_data.x86_capability"?

Thanks,
Michael

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2014-02-28  3:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <52D6566C.5050302@oracle.com>
2014-01-16 12:17 ` Could you please answer some questions regarding Solaris PVHVM pvclock support Stefano Stabellini
2014-01-24  0:21   ` Mukesh Rathor
2014-02-26 11:52   ` Qin Li
2014-02-27 13:03     ` Stefano Stabellini
2014-02-28  3:27       ` Qin Li [this message]
2014-02-28 15:04         ` 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=53100204.1050801@oracle.com \
    --to=qin.l.li@oracle.com \
    --cc=roger.pau@citrix.com \
    --cc=stefano.stabellini@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 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.