WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH] libvchan: interdomain communications library

At 14:52 -0400 on 24 Aug (1314197572), Daniel De Graaf wrote:
> Agreed, barriers are needed for a robust implementation. Since this is
> a shared library and not xen or kernel code, the existing barrier()/wmb()
> functions are not available. The only existing implementations in Xen
> appear to expand to asm("":::"memory") which does not actually implement
> a memory barrier (i.e. MFENCE or similar opcodes).

AIUI on x86_64, writes are guaranteed to be seen in order so the only
thing that barrier has to protect against is the compiler reordering the
writes.

Tim.

-- 
Tim Deegan <tim@xxxxxxx>
Principal Software Engineer, Xen Platform Team
Citrix Systems UK Ltd.  (Company #02937203, SL9 0BG)

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