From: John Snow <jsnow@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: jcody@redhat.com
Subject: Re: [Qemu-devel] [PATCH 10/10] blockjob: use deferred_to_main_loop to indicate the coroutine has ended
Date: Fri, 7 Apr 2017 21:32:58 -0400 [thread overview]
Message-ID: <04b67e67-6b27-e5d0-5fbd-38ec98d57b44@redhat.com> (raw)
In-Reply-To: <20170323173928.14439-11-pbonzini@redhat.com>
On 03/23/2017 01:39 PM, Paolo Bonzini wrote:
> All block jobs are using block_job_defer_to_main_loop as the final
> step just before the coroutine terminates. At this point,
> block_job_enter should do nothing, but currently it restarts
> the freed coroutine.
>
> Now, the job->co states should probably be changed to an enum
> (e.g. BEFORE_START, STARTED, YIELDED, COMPLETED) subsuming
Yes, I'd love to formalize the FSM for jobs.
> block_job_started, job->deferred_to_main_loop and job->busy.
> For now, this patch eliminates the problematic reenter by
> removing the reset of job->deferred_to_main_loop (which served
> no purpose, as far as I could see) and checking the flag in
> block_job_enter.
Not sure -- the original commit 794f01414 makes it seem like it should
stay so that the correct AIO context can be acquired. Probably a race as
jobs don't often stay long once they've deferred to the main loop, but I
think the reset is harmless as you say.
>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> blockjob.c | 10 ++++++++--
> include/block/blockjob_int.h | 3 ++-
> 2 files changed, 10 insertions(+), 3 deletions(-)
>
> diff --git a/blockjob.c b/blockjob.c
> index 3fa2885..2d80dae 100644
> --- a/blockjob.c
> +++ b/blockjob.c
> @@ -750,7 +750,14 @@ void block_job_resume_all(void)
>
> void block_job_enter(BlockJob *job)
> {
> - if (job->co && !job->busy) {
> + if (!block_job_started(job)) {
> + return;
> + }
> + if (job->deferred_to_main_loop) {
> + return;
> + }
> +
> + if (!job->busy) {
> qemu_coroutine_enter(job->co);
> }
> }
> @@ -874,7 +881,6 @@ static void block_job_defer_to_main_loop_bh(void *opaque)
> aio_context_acquire(aio_context);
> }
>
> - data->job->deferred_to_main_loop = false;
> data->fn(data->job, data->opaque);
>
> if (aio_context != data->aio_context) {
> diff --git a/include/block/blockjob_int.h b/include/block/blockjob_int.h
> index 97ffc43..4d287ba 100644
> --- a/include/block/blockjob_int.h
> +++ b/include/block/blockjob_int.h
> @@ -227,7 +227,8 @@ typedef void BlockJobDeferToMainLoopFn(BlockJob *job, void *opaque);
> * @fn: The function to run in the main loop
> * @opaque: The opaque value that is passed to @fn
> *
> - * Execute a given function in the main loop with the BlockDriverState
> + * This function must be called by the main job coroutine just before it
> + * returns. @fn is executed in the main loop with the BlockDriverState
> * AioContext acquired. Block jobs must call bdrv_unref(), bdrv_close(), and
> * anything that uses bdrv_drain_all() in the main loop.
> *
>
Reviewed-by: John Snow <jsnow@redhat.com>
next prev parent reply other threads:[~2017-04-08 1:33 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-23 17:39 [Qemu-devel] [PATCH for-2.10 00/10] Preparation for block job mutex Paolo Bonzini
2017-03-23 17:39 ` [Qemu-devel] [PATCH 01/10] blockjob: remove unnecessary check Paolo Bonzini
2017-04-07 22:30 ` John Snow
2017-04-07 22:54 ` Philippe Mathieu-Daudé
2017-04-07 23:16 ` John Snow
2017-04-10 9:27 ` Stefan Hajnoczi
2017-03-23 17:39 ` [Qemu-devel] [PATCH 02/10] blockjob: remove iostatus_reset callback Paolo Bonzini
2017-04-07 23:12 ` John Snow
2017-04-08 0:18 ` Philippe Mathieu-Daudé
2017-04-10 9:27 ` Stefan Hajnoczi
2017-03-23 17:39 ` [Qemu-devel] [PATCH 03/10] blockjob: introduce block_job_fail Paolo Bonzini
2017-04-07 23:24 ` John Snow
2017-04-10 9:22 ` Stefan Hajnoczi
2017-04-11 4:00 ` Paolo Bonzini
2017-03-23 17:39 ` [Qemu-devel] [PATCH 04/10] blockjob: introduce block_job_pause/resume_all Paolo Bonzini
2017-04-07 23:37 ` John Snow
2017-04-10 9:26 ` Stefan Hajnoczi
2017-03-23 17:39 ` [Qemu-devel] [PATCH 05/10] blockjob: separate monitor and blockjob APIs Paolo Bonzini
2017-04-08 0:03 ` John Snow
2017-04-08 9:52 ` Paolo Bonzini
2017-04-10 16:05 ` John Snow
2017-04-11 4:57 ` Paolo Bonzini
2017-04-11 16:19 ` John Snow
2017-04-10 9:30 ` Stefan Hajnoczi
2017-03-23 17:39 ` [Qemu-devel] [PATCH 06/10] blockjob: move iostatus reset inside block_job_user_resume Paolo Bonzini
2017-04-08 0:28 ` John Snow
2017-04-10 9:33 ` Stefan Hajnoczi
2017-03-23 17:39 ` [Qemu-devel] [PATCH 07/10] blockjob: strengthen a bit test-blockjob-txn Paolo Bonzini
2017-04-08 0:37 ` John Snow
2017-04-10 9:35 ` Stefan Hajnoczi
2017-03-23 17:39 ` [Qemu-devel] [PATCH 08/10] blockjob: introduce block_job_cancel_async Paolo Bonzini
2017-04-08 1:13 ` John Snow
2017-04-08 9:54 ` Paolo Bonzini
2017-04-10 9:36 ` Stefan Hajnoczi
2017-03-23 17:39 ` [Qemu-devel] [PATCH 09/10] blockjob: reorganize block_job_completed_txn_abort Paolo Bonzini
2017-04-08 1:15 ` John Snow
2017-04-08 10:03 ` Paolo Bonzini
2017-04-10 9:44 ` Stefan Hajnoczi
2017-04-10 19:17 ` John Snow
2017-04-11 4:11 ` Paolo Bonzini
2017-03-23 17:39 ` [Qemu-devel] [PATCH 10/10] blockjob: use deferred_to_main_loop to indicate the coroutine has ended Paolo Bonzini
2017-04-08 1:32 ` John Snow [this message]
2017-04-08 9:56 ` Paolo Bonzini
2017-04-10 9:46 ` 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=04b67e67-6b27-e5d0-5fbd-38ec98d57b44@redhat.com \
--to=jsnow@redhat.com \
--cc=jcody@redhat.com \
--cc=pbonzini@redhat.com \
--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).