All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerone Young <jerone@gmail.com>
To: Jerone Young <jyoung5@us.ibm.com>
Cc: xen-devel <xen-devel@lists.sourceforge.net>,
	Keir Fraser <Keir.Fraser@cl.cam.ac.uk>,
	Anthony Liguori <aliguor@us.ibm.com>
Subject: Re: [PATCH] cpu barriers moved and x86-64 barriers add
Date: Thu, 3 Mar 2005 11:27:52 +1800	[thread overview]
Message-ID: <9f50a7a0050302092715ab8466@mail.gmail.com> (raw)
In-Reply-To: <1109715878.13010.34.camel@thinkpad>

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@us.ibm.com> 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@us.ibm.com>
> 
> 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@us.ibm.com
> 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

  reply	other threads:[~2005-03-02 17:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-01 19:56 x86-64 tools fix question Jerone Young
2005-03-01 20:37 ` Keir Fraser
2005-03-01 21:23   ` Anthony Liguori
2005-03-01 22:24     ` [PATCH] cpu barriers moved and x86-64 barriers add Jerone Young
2005-03-02 17:27       ` Jerone Young [this message]
2005-03-02  6:40 ` x86-64 tools fix question David Hopwood
2005-03-02  6:52   ` Anthony Liguori

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9f50a7a0050302092715ab8466@mail.gmail.com \
    --to=jerone@gmail.com \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=aliguor@us.ibm.com \
    --cc=jyoung5@us.ibm.com \
    --cc=xen-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.