From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:60639)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <lcapitulino@redhat.com>) id 1S75de-0000kC-7D
	for qemu-devel@nongnu.org; Mon, 12 Mar 2012 09:50:23 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <lcapitulino@redhat.com>) id 1S75dX-00032X-9D
	for qemu-devel@nongnu.org; Mon, 12 Mar 2012 09:50:13 -0400
Received: from mx1.redhat.com ([209.132.183.28]:59646)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <lcapitulino@redhat.com>) id 1S75dX-00030o-0e
	for qemu-devel@nongnu.org; Mon, 12 Mar 2012 09:50:07 -0400
Date: Mon, 12 Mar 2012 10:50:04 -0300
From: Luiz Capitulino <lcapitulino@redhat.com>
Message-ID: <20120312105004.4a7e1f50@doriath.home>
In-Reply-To: <4F5DB72A.2080906@cn.fujitsu.com>
References: <20120307133644.63d2e662@doriath.home>
	<jj85um$n9b$1@dough.gmane.org> <4F579C86.9000703@codemonkey.ws>
	<20120307151240.13ceb6e7@doriath.home>
	<4F5DB72A.2080906@cn.fujitsu.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] QAPI conversion status and async commands support
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Wen Congyang <wency@cn.fujitsu.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, Eric Blake <eblake@redhat.com>, qemu-devel@nongnu.org, Anthony Liguori <anthony@codemonkey.ws>

On Mon, 12 Mar 2012 16:43:22 +0800
Wen Congyang <wency@cn.fujitsu.com> wrote:

> > Having said that, I wonder if postponing want-to-be-async commands to 1.2 is
> > a good thing. Two solutions other than waiting:
> > 
> >  1. Add synchronous versions of them, if possible (I think this is possible
> >     for the dump command)
> 
> I agree with this. libvirt uses migrate command to do dump now, and it cannot work
> when the guest uses host's device. We need to fix this bug as quickly as possible.
> So we need dump command recently. So I think we can add synchronous versions of
> dump command. Is it OK? If it is OK, I will send the synchronous versions of
> dump command.

I'd be fine with this because this command is expected to be used when the guest
crashes, right? In this case, I _guess_ that holding the global mutex for a long
time is not the end of the world, as the world has ended already :) Far from ideal,
of course, but is the best we can do right now.

Anthony, do you have objections?