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

Re: [Xen-devel] [Patch 2/4] Refining Xsave/Xrestore support


  • To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
  • From: Haitao Shan <maillists.shan@xxxxxxxxx>
  • Date: Thu, 28 Oct 2010 10:57:15 +0800
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, "Han, Weidong" <weidong.han@xxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
  • Delivery-date: Wed, 27 Oct 2010 19:58:09 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=ZrSRU2EbfsHH/sKoF8bXG6KWl9fQfMcZdog2W+Zfi3ifFWM8SncuGew3OCdQ4fcolw rQyxFrs4LvN3rZhlziKE2eoi0KuzQx/3LbCoduWJeBjw+9MMqiD6tVE0j9mqdOQszS8A tn+sukhNHfdfimZQyJshkNs4pxBz4tEJdAa8U=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hi, Jeremy,

My approach is based an old PV-OPS kernel source. Kernel tries to set
CR4.OSXSAVE and read it back to determine whether Xsave is actually
available.
Could you still use that?

Shan Haitao

2010/10/28 Jeremy Fitzhardinge <jeremy@xxxxxxxx>:
>  On 10/27/2010 12:04 AM, Haitao Shan wrote:
>> Hi, Keir,
>>
>> This is patch #2, which adds PV guest Xsave support.
>
> How does a PV guest know whether Xsave support is available?  Previous
> versions of Xen left the xsave cpu feature flag set even though xsave
> wasn't usable by the domain, so I had to forceably mask it from the
> cpuid features within the domain.  Given that a PV domain can't rely on
> X86_FEATURE_XSAVE, how can it tell that the feature is actually usable?
>
> Thanks,
>    J
>

_______________________________________________
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®.