[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Re: [Patch 0/3] Refining Xsave/Xrestore support - Version 3


  • To: Haitao Shan <maillists.shan@xxxxxxxxx>
  • From: Keir Fraser <keir@xxxxxxx>
  • Date: Thu, 04 Nov 2010 07:26:51 +0000
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Tim Deegan <Tim.Deegan@xxxxxxxxxx>
  • Delivery-date: Thu, 04 Nov 2010 00:27:28 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=wnTyD+is6E4UzakrtXIOsjLNv7c8Pjj8TbhtigLgHtjLCrvDVP9F6INLmVU44u+zLR 6zPc8KatW4l8/uHIVods/IOM5GHId7db1K2mZXxmwLaQdEUZqP+ejtltG52R/ropgZCX 2Ijnggngi4n53IRbcfW4+ZNvcOCVU6OZ9YMSc=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Act78aXZNPkn+iKymUay5bKe5lLnQg==
  • Thread-topic: [Xen-devel] Re: [Patch 0/3] Refining Xsave/Xrestore support - Version 3

On 04/11/2010 07:21, "Haitao Shan" <maillists.shan@xxxxxxxxx> wrote:

> OK. I did not realize this was a stable tree. Originally, I thought it
> was a testing tree, which was used for periodic 4.0 update releases.

That is what it is, but it's expected to only have stable patches backported
to it in the first place.

> And by default, xsave is not enabled.

Ah I didn't notice that. This is currently the case even in xen-unstable
too?

> I would agree with you. It is more meaningful when this feature gets
> more tests before doing a backport.

Yes, I think so.

 -- Keir

> Thanks!
> 
> Shan Haitao
> 
> 2010/11/4 Keir Fraser <keir@xxxxxxx>:
>> On 04/11/2010 01:37, "Haitao Shan" <maillists.shan@xxxxxxxxx> wrote:
>> 
>>> Hi, Keir,
>>> 
>>> Can you pull the 4 xsave-related patches to Xen4.0 tree?
>> 
>> Are they really suitable for immediate backport to a stable branch?
>> 
>>  --Keir
>> 
>>> I have tried. Applying the patches is quite straight forward. Patch 4
>>> needs some minor modifications since there are some general function
>>> changes recently in unstable tree (while these are not in Xen4.0). I
>>> have made this for you.
>>> All patches are Signed-off-by: Haitao Shan <haitao.shan@xxxxxxxxx> and
>>> Han Weidong <weidong.han@xxxxxxxxx>
>>> 
>>> Thanks!
>>> 
>>> Shan Haitao
>>> 
>>> 2010/11/2 Haitao Shan <maillists.shan@xxxxxxxxx>:
>>>> Hi, Keir,
>>>> 
>>>> The following patches refines Xen support for CPU Xsave/Xrestore
>>>> support. There are three patches included.
>>>> Patch 1/3:
>>>>  Adding Xsave/Xrestore support for PV guests. Feature is exposed
>>>> via CPUID. XSETBV is trapped and emulated by Xen (via GP#).
>>>> Patch 2/3:
>>>>  Expose AVX to guest OSs.
>>>> Patch 3/3:
>>>>  Adding guest save/restore support when Xsave/Xrestore are available.
>>>>      Adding a pair of hypercalls for PV guest
>>>>      Adding a new data chunk for HVM guest.
>>>> 
>>>> These are version 3 of the patch series.
>>>> 
>>>> Shan Haitao
>>>> 
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>>> http://lists.xensource.com/xen-devel
>> 
>> 
>> 



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.