From: "Dong, Eddie" <eddie.dong@intel.com>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Cc: "Tian, Kevin" <kevin.tian@intel.com>,
"Dong, Eddie" <eddie.dong@intel.com>,
Keir Fraser <keir.fraser@eu.citrix.com>,
"Zhang, Xiantao" <xiantao.zhang@intel.com>
Subject: TSC virtualization across different host frequency platform migration
Date: Wed, 22 Apr 2009 09:32:43 +0800 [thread overview]
Message-ID: <9832F13BD22FB94A829F798DA4A8280501A7D29D36@pdsmsx503.ccr.corp.intel.com> (raw)
In-Reply-To: <49EE71C4.207@jp.fujitsu.com>
[-- Attachment #1: Type: text/plain, Size: 647 bytes --]
Keir and all:
Recently we are considering the potential issue of TSC virtualization across different frequency platform migration. Current approach will lead to synchronization issue between guest TSC and wall clock. Software trap and emulate can solve the problem with the payment of performance overhead which is not optimal. We want to propose smart scaling algorithm which can continuously use HW TSC_OFFSET and maintain long time synchronization of guest TSC. The details are in attached document. Can you have a look and provide comments?
Thanks. BTW of course PV time is another solution which is not covered in this proposal.
Eddie
[-- Attachment #2: tsc-scale2.pdf --]
[-- Type: application/pdf, Size: 228149 bytes --]
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2009-04-22 1:32 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-21 14:17 Xen 4.0 Feature Requests Stephen Spector
2009-04-21 14:53 ` R: " Francesco Gallo
2009-04-22 14:51 ` Kashif Ali
2009-04-22 19:49 ` Alessandro R.
2009-04-23 7:27 ` Robert Dunkley
2009-04-23 13:38 ` Thiago Camargo Martins Cordeiro
2009-04-23 14:34 ` R: [Xen-users] " Robert Dunkley
2009-04-23 15:01 ` R: " Thiago Camargo Martins Cordeiro
2009-04-24 8:50 ` RE: R: [Xen-users] " Kieran Mansley
2009-04-21 16:48 ` Tim Moore
2009-04-21 17:37 ` Paul Schulze
2009-04-21 19:13 ` Jean Guyader
2009-04-22 1:08 ` Dirk Utterback
2009-04-22 1:14 ` Samuel Thibault
2009-04-22 8:08 ` Dirk Utterback
2009-04-22 8:11 ` Samuel Thibault
2009-04-21 18:43 ` Pasi Kärkkäinen
2009-04-21 20:03 ` Andy Burns
2009-04-21 20:10 ` Maximilian Wilhelm
2009-04-22 0:31 ` Philipp Schmid
2009-04-22 1:24 ` Akio Takebe
2009-04-22 1:32 ` Dong, Eddie [this message]
2009-04-22 8:13 ` TSC virtualization across different host frequency platform migration Keir Fraser
2009-04-22 8:49 ` Dong, Eddie
2009-04-22 15:47 ` Dan Magenheimer
2009-04-23 1:28 ` Dong, Eddie
2009-04-23 3:20 ` Tian, Kevin
2009-04-23 3:39 ` Dan Magenheimer
2009-04-23 6:15 ` Tian, Kevin
2009-04-23 13:58 ` Dan Magenheimer
2009-04-22 1:57 ` Xen 4.0 Feature Requests Ryo Tsuruta
2009-04-22 16:14 ` [Xen-devel] " Thiago Camargo Martins Cordeiro
2009-05-03 18:27 ` Sander Eikelenboom
2009-05-03 20:12 ` Paul Schulze
2009-05-04 5:54 ` Re[2]: " Sander Eikelenboom
2009-05-05 14:24 ` Ian Jackson
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=9832F13BD22FB94A829F798DA4A8280501A7D29D36@pdsmsx503.ccr.corp.intel.com \
--to=eddie.dong@intel.com \
--cc=keir.fraser@eu.citrix.com \
--cc=kevin.tian@intel.com \
--cc=xen-devel@lists.xensource.com \
--cc=xiantao.zhang@intel.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.