From: Jeff Cody <jcody@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-block@nongnu.org, mreitz@redhat.com, stefanha@redhat.com,
pbonzini@redhat.com, famz@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH for-2.11 0/4] Fix qemu-iotests failures
Date: Tue, 28 Nov 2017 10:56:47 -0500 [thread overview]
Message-ID: <20171128155647.GA25110@localhost.localdomain> (raw)
In-Reply-To: <20171128154350.21504-1-kwolf@redhat.com>
On Tue, Nov 28, 2017 at 04:43:46PM +0100, Kevin Wolf wrote:
> This reverts the recent fix for the case of qemu-iotests 200 (block job
> completion races when using a separate I/O thread) that only fixed a
> symptom and caused many regressions, and replaces it with a new
> solution that hopefully attacks the right root cause.
>
> The series also contains a bonus fix for a bug that was uncovered by the
> different timing with the patches that are reverted here.
>
> Kevin Wolf (4):
> Revert "coroutine: abort if we try to schedule or enter a pending
> coroutine"
> Revert "blockjob: do not allow coroutine double entry or
> entry-after-completion"
> coroutine: Cancel aio_co_schedule() on direct entry
> block: Expect graph changes in bdrv_parent_drained_begin/end
>
> include/block/blockjob_int.h | 3 +--
> include/qemu/coroutine_int.h | 14 ++++----------
> block/io.c | 8 ++++----
> blockjob.c | 7 ++-----
> util/async.c | 26 +++++++++++++-------------
> util/qemu-coroutine-sleep.c | 12 ------------
> util/qemu-coroutine.c | 31 +++++++++++++++++--------------
> 7 files changed, 41 insertions(+), 60 deletions(-)
>
> --
> 2.13.6
>
Tested-by: Jeff Cody <jcody@redhat.com>
next prev parent reply other threads:[~2017-11-28 15:57 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-28 15:43 [Qemu-devel] [PATCH for-2.11 0/4] Fix qemu-iotests failures Kevin Wolf
2017-11-28 15:43 ` [Qemu-devel] [PATCH for-2.11 1/4] Revert "coroutine: abort if we try to schedule or enter a pending coroutine" Kevin Wolf
2017-11-28 16:00 ` Jeff Cody
2017-11-28 16:18 ` Paolo Bonzini
2017-11-28 16:37 ` Kevin Wolf
2017-11-28 17:01 ` Paolo Bonzini
2017-11-28 17:19 ` Kevin Wolf
2017-11-28 17:33 ` Jeff Cody
2017-11-28 17:35 ` Paolo Bonzini
2017-11-28 15:43 ` [Qemu-devel] [PATCH for-2.11 2/4] Revert "blockjob: do not allow coroutine double entry or entry-after-completion" Kevin Wolf
2017-11-28 16:00 ` Jeff Cody
2017-11-28 15:43 ` [Qemu-devel] [PATCH for-2.11 3/4] coroutine: Cancel aio_co_schedule() on direct entry Kevin Wolf
2017-11-28 16:09 ` Jeff Cody
2017-11-28 16:14 ` Paolo Bonzini
2017-11-28 16:28 ` Kevin Wolf
2017-11-28 16:42 ` Jeff Cody
2017-11-28 16:51 ` Paolo Bonzini
2017-11-28 17:09 ` Jeff Cody
2017-11-28 17:14 ` Paolo Bonzini
2017-11-28 17:03 ` Kevin Wolf
2017-11-28 16:45 ` Paolo Bonzini
2017-11-28 16:30 ` Fam Zheng
2017-11-28 16:46 ` Eric Blake
2017-11-28 15:43 ` [Qemu-devel] [PATCH for-2.11 4/4] block: Expect graph changes in bdrv_parent_drained_begin/end Kevin Wolf
2017-11-28 16:10 ` Jeff Cody
2017-11-28 15:56 ` Jeff Cody [this message]
2017-11-28 16:00 ` [Qemu-devel] [PATCH for-2.11 0/4] Fix qemu-iotests failures Stefan Hajnoczi
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=20171128155647.GA25110@localhost.localdomain \
--to=jcody@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@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).