From: Stefan Hajnoczi <stefanha@gmail.com>
To: Fam Zheng <famz@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
stefanha@redhat.com, qemu-devel@nongnu.org,
qemu-block@nongnu.org, mreitz@redhat.com
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH 1/2] blockjob: Rename block_job_defer_to_main_loop
Date: Thu, 28 Jan 2016 11:53:55 +0000 [thread overview]
Message-ID: <20160128115355.GG7206@stefanha-x1.localdomain> (raw)
In-Reply-To: <1453964571-23016-2-git-send-email-famz@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1852 bytes --]
On Thu, Jan 28, 2016 at 03:02:50PM +0800, Fam Zheng wrote:
> diff --git a/include/block/blockjob.h b/include/block/blockjob.h
> index d84ccd8..de59fc2 100644
> --- a/include/block/blockjob.h
> +++ b/include/block/blockjob.h
> @@ -393,18 +393,20 @@ BlockErrorAction block_job_error_action(BlockJob *job, BlockDriverState *bs,
> typedef void BlockJobDeferToMainLoopFn(BlockJob *job, void *opaque);
>
> /**
> - * block_job_defer_to_main_loop:
> + * block_job_coroutine_complete:
> * @job: The job
> * @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
> - * AioContext acquired. Block jobs must call bdrv_unref(), bdrv_close(), and
> - * anything that uses bdrv_drain_all() in the main loop.
> + * Complete the block job coroutine and execute a given function in the main
This function does not "complete the block job coroutine" so this seems
confusing to me. How about "Call this function to schedule clean up
code to run in the main loop when completing a block job"?
That said, I'm not sure if changing the scope of this function is
necessary at all. If the next patch adds a job->aio_context pointer
then it could set the pointer back after calling the user's function
from the main loop. Then this function could also be used in cases
where the job/coroutine stays alive.
> + * 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. After calling this, the block job coroutine should complete right
> + * away, without doing any heavy operations such as I/O or block_job_yield().
"heavy operations" is too vague. What are the specific constraints
here?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-01-28 11:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 7:02 [Qemu-devel] [PATCH 0/2] blockjob: Fix dead loop with block_job_finish_sync on dataplane disks Fam Zheng
2016-01-28 7:02 ` [Qemu-devel] [PATCH 1/2] blockjob: Rename block_job_defer_to_main_loop Fam Zheng
2016-01-28 11:53 ` Stefan Hajnoczi [this message]
2016-01-28 13:14 ` [Qemu-devel] [Qemu-block] " Fam Zheng
2016-01-28 7:02 ` [Qemu-devel] [PATCH 2/2] blockjob: Fix hang in block_job_finish_sync Fam Zheng
2016-01-28 9:10 ` Paolo Bonzini
2016-01-28 10:57 ` Fam Zheng
2016-01-28 12:07 ` [Qemu-devel] [Qemu-block] " 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=20160128115355.GG7206@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@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).