qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
	jjherne@linux.vnet.ibm.com, Fam Zheng <famz@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>, Jeff Cody <jcody@redhat.com>,
	mreitz@redhat.com, Stefan Hajnoczi <stefanha@redhat.com>
Subject: [Qemu-devel] [PATCH v5 1/8] blockjob: move iostatus reset out of block_job_enter()
Date: Thu, 16 Jun 2016 17:56:22 +0100	[thread overview]
Message-ID: <1466096189-6477-2-git-send-email-stefanha@redhat.com> (raw)
In-Reply-To: <1466096189-6477-1-git-send-email-stefanha@redhat.com>

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>
Reviewed-by: Fam Zheng <famz@redhat.com>
Reviewed-by: Paolo Bonzini <pbonzini@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

  reply	other threads:[~2016-06-16 16:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-16 16:56 [Qemu-devel] [PATCH v5 0/8] blockjob: AioContext change support for mirror and backup Stefan Hajnoczi
2016-06-16 16:56 ` Stefan Hajnoczi [this message]
2016-06-16 16:56 ` [Qemu-devel] [PATCH v5 2/8] blockjob: rename block_job_is_paused() Stefan Hajnoczi
2016-06-16 16:56 ` [Qemu-devel] [PATCH v5 3/8] blockjob: add pause points Stefan Hajnoczi
2016-06-16 16:56 ` [Qemu-devel] [PATCH v5 4/8] blockjob: add block_job_get_aio_context() Stefan Hajnoczi
2016-06-16 16:56 ` [Qemu-devel] [PATCH v5 5/8] block: use safe iteration over AioContext notifiers Stefan Hajnoczi
2016-06-16 16:56 ` [Qemu-devel] [PATCH v5 6/8] blockjob: add AioContext attached callback Stefan Hajnoczi
2016-06-16 16:56 ` [Qemu-devel] [PATCH v5 7/8] mirror: follow AioContext change gracefully Stefan Hajnoczi
2016-06-16 16:56 ` [Qemu-devel] [PATCH v5 8/8] backup: " Stefan Hajnoczi
2016-06-16 17:06 ` [Qemu-devel] [PATCH v5 0/8] blockjob: AioContext change support for mirror and backup Paolo Bonzini
2016-06-17 12:11 ` 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=1466096189-6477-2-git-send-email-stefanha@redhat.com \
    --to=stefanha@redhat.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 \
    /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).