All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Dan Magenheimer <dan.magenheimer@oracle.com>,
	"Xu, Dongxiao" <dongxiao.xu@intel.com>,
	"Nakajima, Jun" <jun.nakajima@intel.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Cc: "Dugger, Donald D" <donald.d.dugger@intel.com>
Subject: Re: RE: Saving/Restoring IA32_TSC_AUX MSR
Date: Fri, 11 Dec 2009 08:03:11 +0000	[thread overview]
Message-ID: <C747AD3F.4212%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <ac1d995d-7658-4770-b2fe-14bf4f87d352@default>

On 11/12/2009 02:00, "Dan Magenheimer" <dan.magenheimer@oracle.com> wrote:

> I expect that Keir will not support putting TSC_AUX
> in the context switch code unless it is absolutely
> necessary, as it is certainly expensive to read and
> write to TSC_AUX and this cost will add to every
> context switch of every VM even though very few will
> actually use rdtscp/TSC_AUX.

Well, you'd make it dependent on the guest using TSC_AUX, I suppose. I think
that's going to be pretty rare.

> So I think we need to decide first about approach (1),
> the full faithful implementation of rdtscp.

The question has to be: what win do we get for faithful virtualisation of
RDTSCP in a virtualised environment? Supporting CPU instructions just
because they're there is not a useful effort.

 -- Keir

  reply	other threads:[~2009-12-11  8:03 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-09 16:41 Saving/Restoring IA32_TSC_AUX MSR Nakajima, Jun
2009-12-09 16:59 ` Dan Magenheimer
2009-12-09 17:07   ` Nakajima, Jun
2009-12-09 17:22     ` Dan Magenheimer
2009-12-10 11:21       ` Xu, Dongxiao
2009-12-10 15:49         ` Dan Magenheimer
2009-12-11  1:22           ` Xu, Dongxiao
2009-12-11  2:00             ` Dan Magenheimer
2009-12-11  8:03               ` Keir Fraser [this message]
2009-12-11  8:43                 ` Zhang, Xiantao
2009-12-11  9:22                   ` Keir Fraser
2009-12-11 15:09                     ` Dan Magenheimer
2009-12-11 15:28                       ` Xu, Dongxiao
2009-12-11 16:12                         ` Dan Magenheimer
2009-12-11 18:38                           ` Nakajima, Jun
2009-12-11 19:46                             ` Dan Magenheimer
2009-12-11 18:20                       ` Jeremy Fitzhardinge
2009-12-11 18:35                         ` Dan Magenheimer
2009-12-11 18:50                           ` Jeremy Fitzhardinge
2009-12-11 19:29                             ` Nakajima, Jun
2009-12-11 22:23                               ` Dan Magenheimer
2009-12-11 22:58                                 ` Nakajima, Jun
2009-12-11 23:30                                   ` Dan Magenheimer
2009-12-11 23:44                                     ` Xu, Dongxiao
2009-12-12  0:09                                       ` Dan Magenheimer
2009-12-12  0:30                                         ` Xu, Dongxiao
2009-12-13  9:17                                 ` Zhang, Xiantao
2009-12-13 18:06                                   ` Dan Magenheimer
2009-12-13 18:59                                     ` Jeremy Fitzhardinge
2009-12-14  6:33                                       ` Xu, Dongxiao

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=C747AD3F.4212%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=dan.magenheimer@oracle.com \
    --cc=donald.d.dugger@intel.com \
    --cc=dongxiao.xu@intel.com \
    --cc=jun.nakajima@intel.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.