xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Shuai Ruan <shuai.ruan@intel.com>, xen-devel@lists.xen.org
Cc: kevin.tian@intel.com, wei.liu2@citrix.com,
	Ian.Campbell@citrix.com, stefano.stabellini@eu.citrix.com,
	eddie.dong@intel.com, ian.jackson@eu.citrix.com,
	jbeulich@suse.com, jun.nakajima@intel.com, keir@xen.org
Subject: Re: [PATCH 0/6] add xsaves/xrstors support
Date: Thu, 2 Jul 2015 15:08:31 +0100	[thread overview]
Message-ID: <559545DF.9060301@citrix.com> (raw)
In-Reply-To: <1435845751-10072-1-git-send-email-shuai.ruan@intel.com>

On 02/07/15 15:02, Shuai Ruan wrote:
> This patchset enable xsaves/xrstors feature.
> It includes tree parts:
> 1. add xsaves/xrstors for xen.
> 2. add xsaves/xrstors for pv guest.
> 3. add xsaves/xrstors for hvn guest.

What is xsaves/xrstors and why might I want Xen to use it? What
advantages does it give? When might these instructions be available?
Where can I read more details about this?

~Andrew

  parent reply	other threads:[~2015-07-02 14:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-02 14:02 [PATCH 0/6] add xsaves/xrstors support Shuai Ruan
2015-07-02 14:02 ` [PATCH 1/6] x86/xsaves: enable xsaves/xrstors for pv guest Shuai Ruan
2015-07-02 14:02 ` [PATCH 2/6] x86/xsaves: enable xsaves/xrstors in xen Shuai Ruan
2015-07-02 14:02 ` [PATCH 3/6] x86/xsaves: enable xsaves/xrstors for hvm guest Shuai Ruan
2015-07-03  8:04   ` Chao Peng
2015-07-02 14:02 ` [PATCH 4/6] libxc: expose xsaves/xgetbv/xsavec to " Shuai Ruan
2015-07-13 16:22   ` Jan Beulich
2015-07-02 14:02 ` [PATCH 5/6] x86/xsaves: support compact format for hvm save/restore Shuai Ruan
2015-07-02 14:02 ` [PATCH 6/6] x86/xsaves: detect xsaves/xgetbv in xen Shuai Ruan
2015-07-02 14:08 ` Andrew Cooper [this message]
2015-07-07  1:46   ` [PATCH 0/6] add xsaves/xrstors support Ruan, Shuai
2015-07-07  9:26     ` Andrew Cooper

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=559545DF.9060301@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=eddie.dong@intel.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=jun.nakajima@intel.com \
    --cc=keir@xen.org \
    --cc=kevin.tian@intel.com \
    --cc=shuai.ruan@intel.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).