Thread (6 messages) flat view 6 messages, 3 authors, 2012-01-22

Re: [PATCH 2/2] virtio: correct the memory barrier in virtqueue_kick_prepare()

From: Rusty Russell <hidden>
Date: 2012-01-22 23:58:34
Also in: kvm, lkml, virtualization

On Sun, 22 Jan 2012 13:47:57 +0200, "Michael S. Tsirkin" [off-list ref] wrote:
On Fri, Jan 20, 2012 at 04:17:08PM +0800, Jason Wang wrote:
quoted
Use virtio_mb() to make sure the available index to be exposed before
checking the the avail event. Otherwise we may get stale value of
avail event in guest and never kick the host after.

Signed-off-by: Jason Wang <redacted>
Good catch.
Note: this fixes a bug introduced by ee7cd8981e15bcb365fc762afe3fc47b8242f630.
Indeed, great catch.  It replaces the missing barrier, and after some
careful thought I've convinced myself that it is necessary for both the
avail index and flag cases.
quoted
 	START_USE(vq);
-	/* Descriptors and available array need to be set before we expose the
-	 * new available array entries. */
-	virtio_wmb(vq);
+	/* We need expose available array entries before checking avail
Nit:
We need expose -> Need to expose
quoted
+	 * event. */
+	virtio_mb(vq);
Fixed typo and applied.

Thanks,
Rusty.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help