From: Stefan Hajnoczi <stefanha@gmail.com>
To: Fam Zheng <famz@redhat.com>
Cc: pbonzini@redhat.com, Stefan Hajnoczi <stefanha@redhat.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH v2 0/4] Fix "stop" draining block jobs
Date: Mon, 20 Apr 2015 16:38:24 +0100 [thread overview]
Message-ID: <20150420153824.GC32653@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1428069921-2957-1-git-send-email-famz@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1406 bytes --]
On Fri, Apr 03, 2015 at 10:05:17PM +0800, Fam Zheng wrote:
> v2: Use "pause" approach as suggested by Paolo.
>
> 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.
>
> Fix this by pausing all the block jobs during bdrv_drain_all.
>
> Please review!
>
> Fam
>
>
> Fam Zheng (4):
> blockjob: Allow nested pause
> block: Pause block jobs in bdrv_drain_all
> qemu-iotests: Test that "stop" doesn't drain block jobs
> blockjob: Update function name in comments
>
> block.c | 20 +++++++++++
> block/backup.c | 2 +-
> block/mirror.c | 4 +--
> blockdev.c | 8 +++--
> blockjob.c | 23 +++++++++----
> include/block/blockjob.h | 20 ++++++++---
> tests/qemu-iotests/129 | 86 ++++++++++++++++++++++++++++++++++++++++++++++
> tests/qemu-iotests/129.out | 5 +++
> tests/qemu-iotests/group | 1 +
> 9 files changed, 153 insertions(+), 16 deletions(-)
> create mode 100644 tests/qemu-iotests/129
> create mode 100644 tests/qemu-iotests/129.out
Thanks, applied to my block-next tree:
https://github.com/stefanha/qemu/commits/block-next
Stefan
[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2015-04-20 15:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-03 14:05 [Qemu-devel] [PATCH v2 0/4] Fix "stop" draining block jobs Fam Zheng
2015-04-03 14:05 ` [Qemu-devel] [PATCH v2 1/4] blockjob: Allow nested pause Fam Zheng
2015-04-03 14:13 ` Paolo Bonzini
2015-04-20 17:11 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2015-04-08 7:25 ` [Qemu-devel] " Alberto Garcia
2015-04-08 10:31 ` Stefan Hajnoczi
2015-04-03 14:05 ` [Qemu-devel] [PATCH v2 2/4] block: Pause block jobs in bdrv_drain_all Fam Zheng
2015-04-07 13:59 ` Alberto Garcia
2015-04-08 10:37 ` Stefan Hajnoczi
2015-04-08 14:56 ` Alberto Garcia
2015-04-09 10:34 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2015-04-03 14:05 ` [Qemu-devel] [PATCH v2 3/4] qemu-iotests: Test that "stop" doesn't drain block jobs Fam Zheng
2015-04-07 14:46 ` Alberto Garcia
2015-04-08 10:39 ` Stefan Hajnoczi
2015-04-24 15:43 ` [Qemu-devel] [Qemu-block] " Max Reitz
2015-04-27 5:14 ` Fam Zheng
2015-04-27 11:08 ` Max Reitz
2015-04-03 14:05 ` [Qemu-devel] [PATCH v2 4/4] blockjob: Update function name in comments Fam Zheng
2015-04-07 14:46 ` Alberto Garcia
2015-04-08 10:40 ` [Qemu-devel] [PATCH v2 0/4] Fix "stop" draining block jobs Stefan Hajnoczi
2015-04-20 15:38 ` Stefan Hajnoczi [this message]
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=20150420153824.GC32653@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=famz@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).