From: Avi Kivity <avi@redhat.com>
To: Sheng Yang <sheng@linux.intel.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
kvm@vger.kernel.org, Dexuan Cui <dexuan.cui@intel.com>
Subject: Re: [PATCH v8 1/2] KVM: VMX: Enable XSAVE/XRSTOR for guest
Date: Thu, 10 Jun 2010 12:05:05 +0300 [thread overview]
Message-ID: <4C10AAC1.1020307@redhat.com> (raw)
In-Reply-To: <1276140433-29570-1-git-send-email-sheng@linux.intel.com>
On 06/10/2010 06:27 AM, Sheng Yang wrote:
> From: Dexuan Cui<dexuan.cui@intel.com>
>
> This patch enable guest to use XSAVE/XRSTOR instructions.
>
> We assume that host_xcr0 would use all possible bits that OS supported.
>
> And we loaded xcr0 in the same way we handled fpu - do it as late as we can.
>
>
Looks good. Will wait for Marcelo to review before applying.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-06-10 9:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-10 3:27 [PATCH v8 1/2] KVM: VMX: Enable XSAVE/XRSTOR for guest Sheng Yang
2010-06-10 3:27 ` [PATCH 2/2] KVM: x86: XSAVE/XRSTOR live migration support Sheng Yang
2010-06-10 9:19 ` Avi Kivity
2010-06-10 9:05 ` Avi Kivity [this message]
2010-06-10 18:27 ` [PATCH v8 1/2] KVM: VMX: Enable XSAVE/XRSTOR for guest Marcelo Tosatti
2010-06-11 5:15 ` Avi Kivity
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=4C10AAC1.1020307@redhat.com \
--to=avi@redhat.com \
--cc=dexuan.cui@intel.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=sheng@linux.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 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).