From: Fam Zheng <famz@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>, pbonzini@redhat.com
Cc: qemu-block@nongnu.org, mreitz@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC PATCH 0/5] Fix some jobs/drain/aio_poll related hangs
Date: Tue, 21 Aug 2018 14:08:34 +0800 [thread overview]
Message-ID: <20180821060834.GL10682@lemon.usersys.redhat.com> (raw)
In-Reply-To: <20180817170246.14641-1-kwolf@redhat.com>
On Fri, 08/17 19:02, Kevin Wolf wrote:
> I'm running out of time and will be offline for the next two weeks, so
> I'm just sending out what I have right now. This is probably not ready
> to be merged yet, but if need be, someone else can pick it up. Otherwise
> I'll do that myself when I return.
I'll try take a look at these. But I'll start from
https://bugzilla.redhat.com/show_bug.cgi?id=1609137
>
> This is related to the following bug reports:
> https://bugzilla.redhat.com/show_bug.cgi?id=1614623
> https://bugzilla.redhat.com/show_bug.cgi?id=1601212
>
> Essentially it tries to fix a few deadlocks into which we run when
> running two commit jobs (probably just one example for problematic
> scenarios) on nodes that are in a non-mainloop AioContext (i.e. with
> dataplane).
>
> Obviously, besides verifying that the code changes are actually correct
> as they are, we also want to add some test cases for this. I suppose
> test-bdrv-drain should test for the individual bugs, and a qemu-iotests
> case could try the higher level scenario of multiple commit jobs with
> dataplane.
The test coverage of dataplane is terribly low. Let's think about adding
variants to existing iotests around block jobs at least.
Fam
>
> Kevin Wolf (5):
> blockjob: Wake up BDS when job becomes idle
> tests: Acquire AioContext around job_finish_sync()
> job: Drop AioContext lock around aio_poll()
> block: Drop AioContext lock in bdrv_drain_poll_top_level()
> [WIP] Lock AioContext in bdrv_co_drain_bh_cb()
>
> include/block/blockjob.h | 13 +++++++++++++
> include/qemu/job.h | 9 +++++++++
> block/io.c | 31 ++++++++++++++++++++++++++++++-
> blockjob.c | 18 ++++++++++++++++++
> job.c | 10 ++++++++++
> tests/test-bdrv-drain.c | 6 ++++++
> tests/test-blockjob.c | 6 ++++++
> 7 files changed, 92 insertions(+), 1 deletion(-)
>
> --
> 2.13.6
>
prev parent reply other threads:[~2018-08-21 6:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-17 17:02 [Qemu-devel] [RFC PATCH 0/5] Fix some jobs/drain/aio_poll related hangs Kevin Wolf
2018-08-17 17:02 ` [Qemu-devel] [RFC PATCH 1/5] blockjob: Wake up BDS when job becomes idle Kevin Wolf
2018-08-17 17:02 ` [Qemu-devel] [RFC PATCH 2/5] tests: Acquire AioContext around job_finish_sync() Kevin Wolf
2018-08-24 7:15 ` Fam Zheng
2018-08-17 17:02 ` [Qemu-devel] [RFC PATCH 3/5] job: Drop AioContext lock around aio_poll() Kevin Wolf
2018-08-24 7:22 ` Fam Zheng
2018-09-04 14:44 ` Kevin Wolf
2018-08-17 17:02 ` [Qemu-devel] [RFC PATCH 4/5] block: Drop AioContext lock in bdrv_drain_poll_top_level() Kevin Wolf
2018-08-24 7:24 ` Fam Zheng
2018-09-04 14:50 ` Kevin Wolf
2018-08-17 17:02 ` [Qemu-devel] [RFC PATCH 5/5] [WIP] Lock AioContext in bdrv_co_drain_bh_cb() Kevin Wolf
2018-08-18 10:46 ` [Qemu-devel] [RFC PATCH 0/5] Fix some jobs/drain/aio_poll related hangs no-reply
2018-08-21 6:08 ` Fam Zheng [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=20180821060834.GL10682@lemon.usersys.redhat.com \
--to=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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.