path: root/drivers/virtio/virtio_balloon.c
diff options
authorAdam Litke <agl@us.ibm.com>2009-12-10 16:35:15 -0600
committerRusty Russell <rusty@rustcorp.com.au>2010-02-24 14:22:14 +1030
commit1f34c71afe5115e77a49c4e67720a66e27053e54 (patch)
treef6481c9a5fbafffd2bd8cbf17274fdc75ffc94b7 /drivers/virtio/virtio_balloon.c
parent9564e138b1f6eb137f7149772438d3f3fb3277dd (diff)
virtio: Fix scheduling while atomic in virtio_balloon stats
This is a fix for my earlier patch: "virtio: Add memory statistics reporting to the balloon driver (V4)". I discovered that all_vm_events() can sleep and therefore stats collection cannot be done in interrupt context. One solution is to handle the interrupt by noting that stats need to be collected and waking the existing vballoon kthread which will complete the work via stats_handle_request(). Rusty, is this a saner way of doing business? There is one issue that I would like a broader opinion on. In stats_request, I update vb->need_stats_update and then wake up the kthread. The kthread uses vb->need_stats_update as a condition variable. Do I need a memory barrier between the update and wake_up to ensure that my kthread sees the correct value? My testing suggests that it is not needed but I would like some confirmation from the experts. Signed-off-by: Adam Litke <agl@us.ibm.com> To: Rusty Russell <rusty@rustcorp.com.au> Cc: Anthony Liguori <aliguori@linux.vnet.ibm.com> Cc: linux-kernel@vger.kernel.org Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Diffstat (limited to 'drivers/virtio/virtio_balloon.c')
1 files changed, 18 insertions, 4 deletions
diff --git a/drivers/virtio/virtio_balloon.c b/drivers/virtio/virtio_balloon.c
index cd778b1752b..3db3d242c3e 100644
--- a/drivers/virtio/virtio_balloon.c
+++ b/drivers/virtio/virtio_balloon.c
@@ -51,6 +51,7 @@ struct virtio_balloon
u32 pfns[256];
/* Memory statistics */
+ int need_stats_update;
struct virtio_balloon_stat stats[VIRTIO_BALLOON_S_NR];
@@ -193,20 +194,30 @@ static void update_balloon_stats(struct virtio_balloon *vb)
* the stats queue operates in reverse. The driver initializes the virtqueue
* with a single buffer. From that point forward, all conversations consist of
* a hypervisor request (a call to this function) which directs us to refill
- * the virtqueue with a fresh stats buffer.
+ * the virtqueue with a fresh stats buffer. Since stats collection can sleep,
+ * we notify our kthread which does the actual work via stats_handle_request().
-static void stats_ack(struct virtqueue *vq)
+static void stats_request(struct virtqueue *vq)
struct virtio_balloon *vb;
unsigned int len;
- struct scatterlist sg;
vb = vq->vq_ops->get_buf(vq, &len);
if (!vb)
+ vb->need_stats_update = 1;
+ wake_up(&vb->config_change);
+static void stats_handle_request(struct virtio_balloon *vb)
+ struct virtqueue *vq;
+ struct scatterlist sg;
+ vb->need_stats_update = 0;
+ vq = vb->stats_vq;
sg_init_one(&sg, vb->stats, sizeof(vb->stats));
if (vq->vq_ops->add_buf(vq, &sg, 1, 0, vb) < 0)
@@ -249,8 +260,11 @@ static int balloon(void *_vballoon)
(diff = towards_target(vb)) != 0
+ || vb->need_stats_update
|| kthread_should_stop()
|| freezing(current));
+ if (vb->need_stats_update)
+ stats_handle_request(vb);
if (diff > 0)
fill_balloon(vb, diff);
else if (diff < 0)
@@ -264,7 +278,7 @@ static int virtballoon_probe(struct virtio_device *vdev)
struct virtio_balloon *vb;
struct virtqueue *vqs[3];
- vq_callback_t *callbacks[] = { balloon_ack, balloon_ack, stats_ack };
+ vq_callback_t *callbacks[] = { balloon_ack, balloon_ack, stats_request };
const char *names[] = { "inflate", "deflate", "stats" };
int err, nvqs;