All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Levon <levon@movementarian.org>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: Ian Pratt <Ian.Pratt@eu.citrix.com>,
	xen-devel@lists.xensource.com,
	Keir Fraser <Keir.Fraser@eu.citrix.com>,
	"Zhang, Xiantao" <xiantao.zhang@intel.com>
Subject: Re: [PATCH] TSC scaling for live migration between platforms with different TSC frequecies
Date: Thu, 18 Jun 2009 12:45:35 -0400	[thread overview]
Message-ID: <20090618164535.GA30082@movementarian.org> (raw)
In-Reply-To: <8ef68a49-a145-4de2-898c-ab5e27937028@default>

On Thu, Jun 18, 2009 at 08:58:49AM -0700, Dan Magenheimer wrote:

> Other apps (and/or the OS kernel) may use TSC to
> approximate the passage of time, and for these apps
> (and gettimeofday in the Linux kernel), this TSC scaling
> patch is a must.  Unfortunately, both kinds of apps could
> be running simultaneously on the same guest.  And
> in either case, RDTSC frequency may be quite high.

Certainly Solaris relies on the TSC for time-keeping, and uses it very
heavily. To the extent that I doubt it's even feasible to migrate to a
machine where scaling needs to be done, and such a migration should be
refused, since it would essentially kill the guest.

> question is:  If it is important to ALWAYS emulate RDTSC,
> can the Xen code be written to handle RDTSC emulation
> much faster?  If it could be made fast enough, the

I'd be amazed if this were possible.

regards
john

  reply	other threads:[~2009-06-18 16:45 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-18  2:56 [PATCH] TSC scaling for live migration between platforms with different TSC frequecies Zhang, Xiantao
2009-06-18  7:37 ` [PATCH] TSC scaling for live migration betweenplatforms " Jan Beulich
2009-06-18  8:52   ` Zhang, Xiantao
2009-06-18 15:40     ` Dan Magenheimer
2009-06-19  1:48       ` Zhang, Xiantao
2009-06-18  9:02 ` [PATCH] TSC scaling for live migration between platforms " Tim Deegan
2009-06-18  9:46   ` Zhang, Xiantao
2009-06-18  9:56     ` Tim Deegan
2009-06-18  9:10 ` Patrick Colp
2009-06-18  9:27   ` Tim Deegan
2009-06-18  9:47     ` Zhang, Xiantao
2009-06-18 15:45       ` Dan Magenheimer
2009-06-18 16:04         ` Tim Deegan
2009-06-18 20:07           ` Dan Magenheimer
2009-06-18 10:56 ` Ian Pratt
2009-06-18 15:58   ` Dan Magenheimer
2009-06-18 16:45     ` John Levon [this message]
2009-06-18 20:27       ` Dan Magenheimer
2009-06-18 20:45         ` John Levon
2009-06-18 20:57           ` Dan Magenheimer
2009-06-18 21:00             ` John Levon
2009-06-18 22:27               ` Dan Magenheimer
2009-06-19 13:36                 ` John Levon
2009-06-19  1:21               ` Zhang, Xiantao
2009-06-19 13:54                 ` John Levon
2009-06-18 23:49       ` Dong, Eddie
2009-06-19  2:25       ` Zhang, Xiantao
2009-06-19 13:53         ` John Levon
2009-06-19 15:07           ` Zhang, Xiantao
2009-06-19 20:44             ` Dan Magenheimer
2009-06-22  1:38               ` Zhang, Xiantao
2009-06-19  1:34   ` Zhang, Xiantao
2009-06-22  5:14 ` Zhang, Xiantao
2009-06-23 10:18   ` Keir Fraser
2009-06-24  1:18     ` Zhang, Xiantao

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=20090618164535.GA30082@movementarian.org \
    --to=levon@movementarian.org \
    --cc=Ian.Pratt@eu.citrix.com \
    --cc=Keir.Fraser@eu.citrix.com \
    --cc=dan.magenheimer@oracle.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.