From: Jeff Cody <jcody@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, famz@redhat.com, qemu-block@nongnu.org,
kwolf@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/4] blockjob: reinstate busy=false/busy=true in block_job_sleep_ns
Date: Wed, 29 Nov 2017 08:13:58 -0500 [thread overview]
Message-ID: <20171129131358.GE18521@localhost.localdomain> (raw)
In-Reply-To: <20171129102513.9153-1-pbonzini@redhat.com>
On Wed, Nov 29, 2017 at 11:25:09AM +0100, Paolo Bonzini wrote:
> In order to avoid reentering a scheduled coroutine this series uses
> a QEMUTimer outside co_aio_sleep_ns. The timer callback just calls
> block_job_enter, and can be easily cancelled with timer_del.
>
> This fixes the outstanding issues with block jobs, without reverting
> the new checks that Jeff added.
>
> I have not run the full qemu-iotests suite, but the main affected
> tests (030, 041, 055, 097, 176, 200) work fine.
>
> Paolo
>
> Kevin Wolf (1):
> block: Expect graph changes in bdrv_parent_drained_begin/end
>
> Paolo Bonzini (3):
> blockjob: remove clock argument from block_job_sleep_ns
> blockjob: introduce block_job_do_yield
> blockjob: reimplement block_job_sleep_ns to allow cancellation
>
> block/backup.c | 4 +--
> block/commit.c | 2 +-
> block/io.c | 8 ++---
> block/mirror.c | 6 ++--
> block/stream.c | 2 +-
> blockjob.c | 76 ++++++++++++++++++++++++++++++++++----------
> include/block/blockjob.h | 5 ++-
> include/block/blockjob_int.h | 7 ++--
> tests/test-blockjob-txn.c | 2 +-
> 9 files changed, 79 insertions(+), 33 deletions(-)
>
> --
> 2.14.3
>
For the series:
Tested-By: Jeff Cody <jcody@redhat.com>
next prev parent reply other threads:[~2017-11-29 13:14 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 10:25 [Qemu-devel] [PATCH 0/4] blockjob: reinstate busy=false/busy=true in block_job_sleep_ns Paolo Bonzini
2017-11-29 10:25 ` [Qemu-devel] [PATCH 1/4] block: Expect graph changes in bdrv_parent_drained_begin/end Paolo Bonzini
2017-11-29 12:27 ` [Qemu-devel] [Qemu-block] " Alberto Garcia
2017-11-29 13:44 ` Stefan Hajnoczi
2017-11-29 13:55 ` Kevin Wolf
2017-12-01 10:13 ` Stefan Hajnoczi
2017-11-29 10:25 ` [Qemu-devel] [PATCH 2/4] blockjob: remove clock argument from block_job_sleep_ns Paolo Bonzini
2017-11-29 12:45 ` [Qemu-devel] [Qemu-block] " Alberto Garcia
2017-11-29 13:14 ` [Qemu-devel] " Jeff Cody
2017-11-29 13:55 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2017-11-29 10:25 ` [Qemu-devel] [PATCH 3/4] blockjob: introduce block_job_do_yield Paolo Bonzini
2017-11-29 13:30 ` Jeff Cody
2017-11-29 13:55 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2017-11-29 10:25 ` [Qemu-devel] [PATCH 4/4] blockjob: reimplement block_job_sleep_ns to allow cancellation Paolo Bonzini
2017-11-29 12:54 ` Kevin Wolf
2017-11-29 13:52 ` Jeff Cody
2017-11-29 13:56 ` Jeff Cody
2017-11-29 14:21 ` Kevin Wolf
2017-11-29 14:25 ` Jeff Cody
2017-11-29 14:07 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2017-11-29 21:12 ` [Qemu-devel] " Eric Blake
2017-11-29 13:13 ` Jeff Cody [this message]
2017-11-29 13:14 ` [Qemu-devel] [PATCH 0/4] blockjob: reinstate busy=false/busy=true in block_job_sleep_ns 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=20171129131358.GE18521@localhost.localdomain \
--to=jcody@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--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 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).