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] cpu barriers moved and x86-64 barriers add

To: Jerone Young <jyoung5@xxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] cpu barriers moved and x86-64 barriers add
From: Jerone Young <jerone@xxxxxxxxx>
Date: Thu, 3 Mar 2005 11:27:52 +1800
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxxx>, Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>, Anthony Liguori <aliguor@xxxxxxxxxx>
Delivery-date: Wed, 02 Mar 2005 17:29:27 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=e7E2oxrGNiXosAHjmKCo7ddaz1chaXLKNTGN57oDcGrYp0qWUYpXDgY0o8+XMJhfAcLMU/zLdxH3uYwYGUHSyUnzSwRyJW/F0sQtgvlyFKLTQSx4yuXBWldlZQ/tyojoETfLdkvJj6sd66zkqrxfq72GwwUBv3SHSqv/jUJlyyE=
Envelope-to: xen+James.Bulpin@xxxxxxxxxxxx
In-reply-to: <1109715878.13010.34.camel@thinkpad>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
References: <1109707006.13010.15.camel@thinkpad> <1b8fe72b3f68af920c3ff9bba691daff@xxxxxxxxxxxx> <4224DD54.3000501@xxxxxxxxxx> <1109715878.13010.34.camel@thinkpad>
Reply-to: Jerone Young <jerone@xxxxxxxxx>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
Ok pay this email no mind. This was the first one I sent yesterday.
Something must have happened with the IBM smtp server and caused my
email to be held and outragously long time then sent. Sorry about this
guys.


On Tue, 01 Mar 2005 16:24:37 -0600, Jerone Young <jyoung5@xxxxxxxxxx> wrote:
> We actually should have wmb() be defined as "asm volatile("":::"memory")
> since we are not using out of order io.
> 
> The patch attached removes all the instances and places the definitions
> in libxc/xc.h as per the discussion last week between Anthony & Keir.
> 
> Signed-off-by: Jerone Young <jyoung5@xxxxxxxxxx>
> 
> On Tue, 2005-03-01 at 15:23 -0600, Anthony Liguori wrote:
> > Keir Fraser wrote:
> >
> > >
> > > On 1 Mar 2005, at 19:56, Jerone Young wrote:
> > >
> > >>     I would like to discuss is this correct, dead wrong, or even
> > >> needed at
> > >> all?
> > >
> > >
> > > x86/64 has proper barrier instructions -- see
> > > include/asm-x86_64/system.h in Linux. It is from there that we should
> > > pull our definitions. Barrier macros are defined in a few places in
> > > the tools -- we ought to pull them all into one single header
> > > incorporated by all tools that need it.
> >
> > I was just about to send this out myself :-)  I think the consensus was
> > to put them all in xc.h.  I posted a patch recently that made everything
> > include asm/system.h.  All it should take is replacing asm/system.h with
> > xc.h in the patch and then making the necessary changes to xc.h.
> >
> > For reference, the proper x86-64 barriers are:
> >
> > #define mb()     asm volatile("mfence":::"memory")
> > #define rmb()    asm volatile("lfence":::"memory")
> > #define wmb()    asm volatile("sfence":::"memory")
> >
> > Regards,
> > Anthony Liguori
> >
> --
> Jerone Young
> Open Virtualization
> IBM Linux Technology Center
> jyoung5@xxxxxxxxxx
> 512-838-1157 (T/L: 678-1157)
> 
> 
>


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel

<Prev in Thread] Current Thread [Next in Thread>