From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:48625) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SEjHo-0006w3-Kb for qemu-devel@nongnu.org; Mon, 02 Apr 2012 11:35:25 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SEjHi-00028S-AI for qemu-devel@nongnu.org; Mon, 02 Apr 2012 11:35:16 -0400 Received: from mx1.redhat.com ([209.132.183.28]:38982) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SEjHi-00027s-2P for qemu-devel@nongnu.org; Mon, 02 Apr 2012 11:35:10 -0400 Message-ID: <4F79C7EE.1030604@redhat.com> Date: Mon, 02 Apr 2012 17:38:22 +0200 From: Kevin Wolf MIME-Version: 1.0 References: <1333106233-12472-1-git-send-email-pbonzini@redhat.com> <1333106233-12472-2-git-send-email-pbonzini@redhat.com> In-Reply-To: <1333106233-12472-2-git-send-email-pbonzini@redhat.com> Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 1/4] block: cancel jobs when a device is ready to go away List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: qemu-devel@nongnu.org, stefanha@linux.vnet.ibm.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 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