All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: qemu-devel@nongnu.org, anthony@codemonkey.ws
Subject: [Qemu-devel] [PATCH] qemu/virtio: make wmb compiler barrier + comments
Date: Mon, 26 Oct 2009 15:17:15 +0200	[thread overview]
Message-ID: <20091026131715.GA25271@redhat.com> (raw)

wmb must be at least a compiler barrier, even without SMP.
Further, we likely need some rmb()/mb() as well:
I have not audited the code but lguest has mb(),
add a comment for now.

Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
---
 hw/virtio.c |    5 ++++-
 1 files changed, 4 insertions(+), 1 deletions(-)

diff --git a/hw/virtio.c b/hw/virtio.c
index 337ff27..1f92171 100644
--- a/hw/virtio.c
+++ b/hw/virtio.c
@@ -23,8 +23,11 @@
 /* QEMU doesn't strictly need write barriers since everything runs in
  * lock-step.  We'll leave the calls to wmb() in though to make it obvious for
  * KVM or if kqemu gets SMP support.
+ * In any case, we must prevent the compiler from reordering the code.
+ * TODO: we likely need some rmb()/mb() as well.
  */
-#define wmb() do { } while (0)
+
+#define wmb() __asm__ __volatile__("": : :"memory")
 
 typedef struct VRingDesc
 {
-- 
1.6.5.rc2

             reply	other threads:[~2009-10-26 13:19 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-26 13:17 Michael S. Tsirkin [this message]
2009-11-11  1:34 ` [Qemu-devel] [PATCH] qemu/virtio: make wmb compiler barrier + comments Paul Brook
2009-11-11  9:37   ` [Qemu-devel] " Michael S. Tsirkin
2009-11-11 13:01     ` Paul Brook
2009-11-11 13:12       ` Michael S. Tsirkin
2009-11-11 13:45         ` Paul Brook
2009-11-11 14:08           ` Michael S. Tsirkin
2009-11-11 14:16             ` Paul Brook
2009-11-11 14:34               ` Michael S. Tsirkin
2009-11-11 16:13                 ` Paul Brook
2009-11-11 17:18             ` Scott Tsai
2009-11-11 18:08               ` Michael S. Tsirkin
2009-11-11 18:09               ` Michael S. Tsirkin
2009-11-11 18:37                 ` Scott Tsai
2009-11-11 19:56                   ` Michael S. Tsirkin
2009-11-13  3:00               ` Jamie Lokier
2009-11-11 13:15       ` 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=20091026131715.GA25271@redhat.com \
    --to=mst@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=qemu-devel@nongnu.org \
    /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.