From: Fam Zheng <famz@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: qemu-devel@nongnu.org, Kevin Wolf <kwolf@redhat.com>,
jjherne@linux.vnet.ibm.com, Paolo Bonzini <pbonzini@redhat.com>,
Jeff Cody <jcody@redhat.com>,
mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH v4 1/5] blockjob: move iostatus reset out of block_job_enter()
Date: Wed, 15 Jun 2016 16:47:33 +0800 [thread overview]
Message-ID: <20160615084733.GC14453@ad.usersys.redhat.com> (raw)
In-Reply-To: <1465928228-1184-2-git-send-email-stefanha@redhat.com>
On Tue, 06/14 19:17, Stefan Hajnoczi wrote:
> The QMP block-job-resume command and cancellation may want to reset the
> job's iostatus. The next patches add a user who does not want to reset
> iostatus so move it up to block_job_enter() callers.
>
> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> ---
> blockdev.c | 1 +
> blockjob.c | 2 +-
> 2 files changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/blockdev.c b/blockdev.c
> index 7fd515a..19b963c 100644
> --- a/blockdev.c
> +++ b/blockdev.c
> @@ -3799,6 +3799,7 @@ void qmp_block_job_resume(const char *device, Error **errp)
>
> job->user_paused = false;
> trace_qmp_block_job_resume(job);
> + block_job_iostatus_reset(job);
> block_job_resume(job);
> aio_context_release(aio_context);
> }
> diff --git a/blockjob.c b/blockjob.c
> index c095cc5..463bccf 100644
> --- a/blockjob.c
> +++ b/blockjob.c
> @@ -269,7 +269,6 @@ void block_job_resume(BlockJob *job)
>
> void block_job_enter(BlockJob *job)
> {
> - block_job_iostatus_reset(job);
> if (job->co && !job->busy) {
> qemu_coroutine_enter(job->co, NULL);
> }
> @@ -278,6 +277,7 @@ void block_job_enter(BlockJob *job)
> void block_job_cancel(BlockJob *job)
> {
> job->cancelled = true;
> + block_job_iostatus_reset(job);
> block_job_enter(job);
> }
>
> --
> 2.5.5
>
Reviewed-by: Fam Zheng <famz@redhat.com>
next prev parent reply other threads:[~2016-06-15 8:47 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 [this message]
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
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=20160615084733.GC14453@ad.usersys.redhat.com \
--to=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 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.