Re: [Xen-devel] [Patch] X86: expose HLE/RTM features to dom0

["Shan, Haitao" <haitao.shan@xxxxxxxxx>]

> - actual use in the hypervisor itself
> - use in Linux (afaict impossible at least for HLE with ticket locks, yet
Jan,
We are working on the first one. I know someone is working on the kernel
side, but I don't know any details.
But HLE should be useful for a lock(not fine grained) for protecting an
in-memory data structure that are actually grasped by different lock holders
to access different data fields(which are non-relevant to each other).
It might not be the cases for Xen hypervisor. We need profile and see.

Shan Haitao

> -----Original Message-----
> From: xen-devel-bounces@xxxxxxxxxxxxx [mailto:xen-devel-
> bounces@xxxxxxxxxxxxx] On Behalf Of Jan Beulich
> Sent: Tuesday, February 28, 2012 4:12 PM
> To: Liu, Jinsong
> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx; keir.xen@xxxxxxxxx; Ian Campbell
> Subject: Re: [Xen-devel] [Patch] X86: expose HLE/RTM features to dom0
> 
> >>> On 28.02.12 at 06:09, "Liu, Jinsong" <jinsong.liu@xxxxxxxxx> wrote:
> > X86: expose HLE/RTM features to dom0
> >
> > Intel recently release 2 new features, HLE and TRM.
> > Refer to http://software.intel.com/file/41417.
> > This patch expose them to dom0.
> 
> While I committed this as obviously correct and desirable, I wonder what
> plans you have with this feature wrt
> - permitting use for HVM guests
> - permitting use in pv DomU
> - actual use in the hypervisor itself
> - use in Linux (afaict impossible at least for HLE with ticket locks, yet
>   HLE is certainly the more desirable first step)
> 
> Thanks, Jan
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxx
> http://lists.xen.org/xen-devel

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel