From: Stefan Hajnoczi <stefanha@gmail.com>
To: Fam Zheng <famz@redhat.com>
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
Kevin Wolf <kwolf@redhat.com>, Jeff Cody <jcody@redhat.com>,
qemu-devel@nongnu.org, mreitz@redhat.com,
jjherne@linux.vnet.ibm.com, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v4 3/5] blockjob: add AioContext attached callback
Date: Thu, 16 Jun 2016 11:13:09 +0100 [thread overview]
Message-ID: <20160616101309.GF31974@stefanha-x1.localdomain> (raw)
In-Reply-To: <20160615090528.GE14453@ad.usersys.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1328 bytes --]
On Wed, Jun 15, 2016 at 05:05:28PM +0800, Fam Zheng wrote:
> On Tue, 06/14 19:17, Stefan Hajnoczi wrote:
> >
> > +static void block_job_attached_aio_context(AioContext *new_context,
> > + void *opaque)
> > +{
> > + BlockJob *job = opaque;
> > +
> > + if (job->driver->attached_aio_context) {
> > + job->driver->attached_aio_context(job, new_context);
> > + }
> > +
> > + block_job_resume(job);
> > +}
> > +
> > +static void block_job_detach_aio_context(void *opaque)
> > +{
> > + BlockJob *job = opaque;
> > +
> > + /* In case the job terminates during aio_poll()... */
> > + block_job_ref(job);
> > +
> > + block_job_pause(job);
> > +
> > + if (!job->paused) {
> > + /* If job is !job->busy this kicks it into the next pause point. */
> > + block_job_enter(job);
> > + }
> > + while (!job->paused && !job->completed) {
> > + aio_poll(blk_get_aio_context(job->blk), true);
>
> For the complete part, we should do it like block_job_finish_sync:
>
> while (!job->completed) {
> aio_poll(job->deferred_to_main_loop ? qemu_get_aio_context() :
> blk_get_aio_context(job->blk),
> true);
> }
Will fix in v5.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-06-16 10:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 18:17 [Qemu-devel] [PATCH v4 0/5] blockjob: AioContext change support for mirror and backup Stefan Hajnoczi
2016-06-14 18:17 ` [Qemu-devel] [PATCH v4 1/5] blockjob: move iostatus reset out of block_job_enter() Stefan Hajnoczi
2016-06-15 8:47 ` Fam Zheng
2016-06-14 18:17 ` [Qemu-devel] [PATCH v4 2/5] blockjob: add pause points Stefan Hajnoczi
2016-06-15 8:53 ` Paolo Bonzini
2016-06-16 13:17 ` Stefan Hajnoczi
2016-06-16 13:24 ` Paolo Bonzini
2016-06-15 8:57 ` Fam Zheng
2016-06-15 9:01 ` Paolo Bonzini
2016-06-16 10:19 ` Stefan Hajnoczi
2016-06-14 18:17 ` [Qemu-devel] [PATCH v4 3/5] blockjob: add AioContext attached callback Stefan Hajnoczi
2016-06-15 9:05 ` Fam Zheng
2016-06-16 10:13 ` Stefan Hajnoczi [this message]
2016-06-14 18:17 ` [Qemu-devel] [PATCH v4 4/5] mirror: follow AioContext change gracefully Stefan Hajnoczi
2016-06-15 8:57 ` Paolo Bonzini
2016-06-16 10:17 ` Stefan Hajnoczi
2016-06-16 10:21 ` Paolo Bonzini
2016-06-16 11:28 ` Stefan Hajnoczi
2016-06-14 18:17 ` [Qemu-devel] [PATCH v4 5/5] backup: " Stefan Hajnoczi
2016-06-14 19:06 ` [Qemu-devel] [PATCH v4 0/5] blockjob: AioContext change support for mirror and backup Jason J. Herne
2016-06-15 8:56 ` Stefan Hajnoczi
2016-06-15 8:59 ` Paolo Bonzini
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=20160616101309.GF31974@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=famz@redhat.com \
--cc=jcody@redhat.com \
--cc=jjherne@linux.vnet.ibm.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--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).