From: Kevin Wolf <kwolf@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, stefanha@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH 1/4] block: cancel jobs when a device is ready to go away
Date: Mon, 02 Apr 2012 17:38:22 +0200 [thread overview]
Message-ID: <4F79C7EE.1030604@redhat.com> (raw)
In-Reply-To: <1333106233-12472-2-git-send-email-pbonzini@redhat.com>
Am 30.03.2012 13:17, schrieb Paolo Bonzini:
> We do not want jobs to keep a device busy for a possibly very long
> time, and management could become confused because they thought a
> device was not even there anymore. So, cancel long-running jobs
> as soon as their device is going to disappear.
>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Shouldn't management tools know what jobs they have running?
We can take this for now, but once we switch to blockdev-add/del,
management tools will have to be explicit about the BlockDriverState
deletion (and I think the right semantics there is that it fails if jobs
are still running).
Kevin
next prev parent reply other threads:[~2012-04-02 15:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-30 11:17 [Qemu-devel] [PATCH 0/4] Job API improvements and bugfixes Paolo Bonzini
2012-03-30 11:17 ` [Qemu-devel] [PATCH 1/4] block: cancel jobs when a device is ready to go away Paolo Bonzini
2012-04-02 15:38 ` Kevin Wolf [this message]
2012-03-30 11:17 ` [Qemu-devel] [PATCH 2/4] block: fix streaming/closing race Paolo Bonzini
2012-03-30 13:32 ` Stefan Hajnoczi
2012-03-30 11:17 ` [Qemu-devel] [PATCH 3/4] block: set job->speed in block_set_speed Paolo Bonzini
2012-03-30 11:17 ` [Qemu-devel] [PATCH 4/4] block: document job API Paolo Bonzini
2012-03-30 13:42 ` [Qemu-devel] [PATCH 0/4] Job API improvements and bugfixes Stefan Hajnoczi
2012-04-02 15:41 ` Kevin Wolf
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=4F79C7EE.1030604@redhat.com \
--to=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.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.