qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
	berto@igalia.com, qemu-block@nongnu.org,
	Jeff Cody <jcody@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	pbonzini@redhat.com
Subject: [Qemu-devel] [PATCH 0/3] Fix "stop" draining block jobs
Date: Fri,  3 Apr 2015 18:38:59 +0800	[thread overview]
Message-ID: <1428057542-24310-1-git-send-email-famz@redhat.com> (raw)

Stopping the vm will drive the block job all the way to the end, because the
sleep duration is too short, which means the block_job_sleep_ns in the block
jobs are unhelpful. That is because the timer will fire too soon, even before
the aio_poll in bdrv_drain_all returns.

Lengthen the sleep and add a test case to catch this issue in the future.

It's not perfect, because the aio_poll returning point could still be far
enough that we wake up the job earlier, but this patch is already making it
better in common cases - setting up a timer with timeout=0 was definitely too
short anyway.

A complete solution would be adding a "sleep until next iteration" timer/BH
API, but I'm not sure that is worth the complexity.

Please review!

Fam

Fam Zheng (3):
  blockjob: Don't sleep meaninglessly short
  qemu-iotests: Test that "stop" doesn't drain block jobs
  blockjob: Update function name in comments

 block/backup.c             |  2 +-
 block/mirror.c             |  2 +-
 blockjob.c                 |  3 +-
 include/block/blockjob.h   |  6 +++-
 tests/qemu-iotests/129     | 86 ++++++++++++++++++++++++++++++++++++++++++++++
 tests/qemu-iotests/129.out |  5 +++
 tests/qemu-iotests/group   |  1 +
 7 files changed, 101 insertions(+), 4 deletions(-)
 create mode 100644 tests/qemu-iotests/129
 create mode 100644 tests/qemu-iotests/129.out

-- 
2.1.0

             reply	other threads:[~2015-04-03 10:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-03 10:38 Fam Zheng [this message]
2015-04-03 10:39 ` [Qemu-devel] [PATCH 1/3] blockjob: Don't sleep meaninglessly short Fam Zheng
2015-04-03 10:39 ` [Qemu-devel] [PATCH 2/3] qemu-iotests: Test that "stop" doesn't drain block jobs Fam Zheng
2015-04-03 10:39 ` [Qemu-devel] [PATCH 3/3] blockjob: Update function name in comments Fam Zheng
2015-04-03 11:10 ` [Qemu-devel] [PATCH 0/3] Fix "stop" draining block jobs Paolo Bonzini
2015-04-03 12:30   ` Fam Zheng

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=1428057542-24310-1-git-send-email-famz@redhat.com \
    --to=famz@redhat.com \
    --cc=berto@igalia.com \
    --cc=jcody@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.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;
as well as URLs for NNTP newsgroup(s).