From: David Gibson <dwg@au1.ibm.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: aliguori@us.ibm.com, aik@ozlabs.ru, rusty@rustcorp.com.au,
qemu-devel@nongnu.org, agraf@suse.de,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] virtio: Make memory barriers be memory barriers
Date: Sun, 4 Sep 2011 00:46:35 +1000 [thread overview]
Message-ID: <20110903144635.GD12965@yookeroo.fritz.box> (raw)
In-Reply-To: <20110902154549.GA18368@redhat.com>
On Fri, Sep 02, 2011 at 06:45:50PM +0300, Michael S. Tsirkin wrote:
> On Thu, Sep 01, 2011 at 04:31:09PM -0400, Paolo Bonzini wrote:
> > > > > Why not limit the change to ppc then?
> > > >
> > > > Because the bug is masked by the x86 memory model, but it is still
> > > > there even there conceptually. It is not really true that x86 does
> > > > not need memory barriers, though it doesn't in this case:
> > > >
> > > > http://bartoszmilewski.wordpress.com/2008/11/05/who-ordered-memory-fences-on-an-x86/
> > > >
> > > > Paolo
> > >
> > > Right.
> > > To summarize, on x86 we probably want wmb and rmb to be compiler
> > > barrier only. Only mb might in theory need to be an mfence.
> >
> > No, wmb needs to be sfence and rmb needs to be lfence. GCC does
> > not provide those, so they should become __sync_synchronize() too,
> > or you should use inline assembly.
> >
> > > But there might be reasons why that is not an issue either
> > > if we look closely enough.
> >
> > Since the ring buffers are not using locked instructions (no xchg
> > or cmpxchg) the barriers simply must be there, even on x86. Whether
> > it works in practice is not interesting, only the formal model is
> > interesting.
> >
> > Paolo
>
> Well, can you describe an issue in virtio that lfence/sfence help solve
> in terms of a memory model please?
> Pls note that guest uses smp_ variants for barriers.
Ok, so, I'm having a bit of trouble with the fact that I'm having to
argue the case that things the protocol requiress to be memory
barriers actually *be* memory barriers on all platforms.
I mean argue for a richer set of barriers, with per-arch minimal
implementations instead of the large but portable hammer of
sync_synchronize, if you will. But just leaving them out on x86!?
Seriously, wtf? Do you enjoy having software that works chiefly by
accident?
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
next prev parent reply other threads:[~2011-09-04 2:32 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-01 6:09 [Qemu-devel] [PATCH] virtio: Make memory barriers be memory barriers David Gibson
2011-09-01 6:47 ` Paolo Bonzini
2011-09-02 0:08 ` David Gibson
2011-09-02 6:49 ` Paolo Bonzini
2011-09-03 11:53 ` Blue Swirl
2011-09-01 7:37 ` Sasha Levin
2011-09-01 7:38 ` Sasha Levin
2011-09-01 7:56 ` Paolo Bonzini
2011-09-02 0:09 ` David Gibson
2011-09-01 15:30 ` Michael S. Tsirkin
2011-09-01 16:14 ` Paolo Bonzini
2011-09-01 16:34 ` Michael S. Tsirkin
2011-09-01 20:31 ` Paolo Bonzini
2011-09-02 15:45 ` Michael S. Tsirkin
2011-09-03 14:46 ` David Gibson [this message]
2011-09-04 9:16 ` Michael S. Tsirkin
2011-09-05 4:43 ` David Gibson
2011-09-05 9:19 ` Michael S. Tsirkin
2011-09-06 3:12 ` David Gibson
2011-09-06 6:55 ` Paolo Bonzini
2011-09-06 9:02 ` David Gibson
2011-09-06 9:28 ` Avi Kivity
2011-09-06 9:35 ` Michael S. Tsirkin
2011-09-06 9:38 ` Paolo Bonzini
2011-09-05 7:41 ` Paolo Bonzini
2011-09-05 8:06 ` Michael S. Tsirkin
2011-09-05 9:42 ` Paolo Bonzini
2011-09-03 16:19 ` Paolo Bonzini
2011-09-04 8:47 ` Michael S. Tsirkin
2011-09-02 0:11 ` David Gibson
2011-09-02 6:11 ` Paolo Bonzini
2011-09-02 15:57 ` Michael S. Tsirkin
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=20110903144635.GD12965@yookeroo.fritz.box \
--to=dwg@au1.ibm.com \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=aliguori@us.ibm.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rusty@rustcorp.com.au \
/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;
as well as URLs for NNTP newsgroup(s).