Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: paulmck@linux.vnet.ibm.com (Paul E. McKenney)
Subject: [ltt-dev] [URCU PATCH] cmm: provide lightweight rmb/wmb on PPC
Date: Wed, 21 Sep 2011 16:42:42 -0700	[thread overview]
Message-ID: <20110921234242.GG2394@linux.vnet.ibm.com> (raw)
In-Reply-To: <4E78C1C5.2080001@redhat.com>

On Tue, Sep 20, 2011 at 06:39:33PM +0200, Paolo Bonzini wrote:
> On 09/20/2011 06:31 PM, Mathieu Desnoyers wrote:
> >I don't think lwsync orders non-cacheable memory operations. Therefore,
> >is it the right choice for cmm_rmb/cmm_wmb ?
> 
> I think you're right. "eieio;lwsync" is good for rmb, lwsync is good
> for wmb/smp_rmb/smp_wmb.

But eieio;lwsync won't order non-cacheable memory operations against
cacheable memory operations.  This means that your MMIO accesses can
slip out of your lock-based critical section, which is a very bad
thing indeed.

For general-purpose use, I strongly recommend full "sync" for mb(),
rmb(), and wmb().  For memory-only use, the developer should not
be using these, but smp_mb(), smp_rmb(), and smp_wmb() instead.

							Thanx, Paul




  parent reply	other threads:[~2011-09-21 23:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-20  7:12 Paolo Bonzini
2011-09-20 16:31 ` Mathieu Desnoyers
2011-09-20 16:39   ` Paolo Bonzini
2011-09-20 16:51     ` Mathieu Desnoyers
2011-09-21  7:20       ` Paolo Bonzini
2011-09-21 23:43         ` Paul E. McKenney
2011-09-21 23:42     ` Paul E. McKenney [this message]
2011-09-22  8:42       ` [ltt-dev] [PATCH v2] cmm: provide lightweight smp_rmb/smp_wmb " Paolo Bonzini
2011-09-22  9:10         ` Mathieu Desnoyers
2011-09-22 14:49         ` Paul E. McKenney
2011-09-22 14:57           ` Mathieu Desnoyers
2011-09-22 15:26             ` Paul E. McKenney

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=20110921234242.GG2394@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox