All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: "Cui, Dexuan" <dexuan.cui@intel.com>, xen-devel@lists.xensource.com
Subject: Re: [PATCH] Add xsave/xrstor support to Xen
Date: Wed, 28 May 2008 13:42:38 +0100	[thread overview]
Message-ID: <C46311CE.21542%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <FE7BBCFBB500984A9A7922EBC95F516E013B4791@pdsmsx414.ccr.corp.intel.com>

I'm missing any context about these new instructions. Why would we use them
rather than FXSAVE/FXRSTOR? They seem to save the same state. Unless the
amount of PV guest state that needs to be saved/restored has actually been
extended then there will be no need to change the cpucontext hypercalls or
the save/restore format.

 -- Keir

On 28/5/08 13:06, "Cui, Dexuan" <dexuan.cui@intel.com> wrote:

> Hi Keir,
> In the xsave/xrstor patch, I don't use "arch.guest_context.fpu_ctxt" any
> longer.
> I use "arch_vcpu.xsave_area" to save the processor extended states.
> 
> Looks this causes trouble for guest's save/restore (including PV guest and HVM
> guest):
> 
> On xsave/xrstor-capable host, to support guest's save/restore, Control Panel
> should save/restore the variable-length "xsave_area", but the current
> hypercall XEN_DOMCTL_{get/set}vcpucontext can't transfer the "xsave_area"
> between Control Panel and hypervisor, so a new hypercall is needed for this?
> Looks it's not very easy to make the codes clean... :(
> 
> Could you give some suggestions?
> 
> Thanks!
> 
> -- Dexuan
> 
> 
> -----Original Message-----
> From: xen-devel-bounces@lists.xensource.com
> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Cui, Dexuan
> Sent: 2008年5月28日 20:03
> To: Keir Fraser; xen-devel@lists.xensource.com
> Subject: [Xen-devel] [PATCH] Add xsave/xrstor support to Xen
> 
> The attached patch adds the support of xsave/xrstor infrastructure for
> x86.
> xsave/xrstor manages the existing and future processor extended states
> in x86 architecture.
> 
> The XSAVE/XRSTOR/XGETBV/XSETBV instructions and the Processor Extended
> State are defined in the Intel SDMs:
> http://www.intel.com/products/processor/manuals/
> 
> The basic ideas of the patch are:
> 1) enable the xsave/xrstor feature when Xen boots;
> 2) xsave/xrstor the related processor states (i.e., FPU/MMX, SSE) on
> vcpu context switch;
> 3) with the xsave/xrstor feature enabled, Xen doesn't intercept HVM
> vcpu's #NM at all, and Xen still intercepts PV vcpu's #NM and forwards
> it into PV vcpu if necessary;
> 4) xsave/xrstor-aware HVM guest is supported in the patch.
> 
> Signed-off-by: Dexuan Cui <dexuan.cui@intel.com>

  reply	other threads:[~2008-05-28 12:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-28 12:02 [PATCH] Add xsave/xrstor support to Xen Cui, Dexuan
2008-05-28 12:06 ` Cui, Dexuan
2008-05-28 12:42   ` Keir Fraser [this message]
2008-05-28 13:11     ` Cui, Dexuan
2008-05-28 13:37       ` Keir Fraser
  -- strict thread matches above, loose matches on Subject: below --
2008-11-26  9:43 [PATCH] Add XSAVE/XRSTOR " Cui, Dexuan
2008-11-26 10:25 ` Keir Fraser
2008-11-26 11:22 ` Jan Beulich
2009-04-04  0:22 [PATCH] Add xsave/xrstor " yuhong

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=C46311CE.21542%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=dexuan.cui@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.