From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MJ7UO-0002nB-Do for qemu-devel@nongnu.org; Tue, 23 Jun 2009 11:00:48 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MJ7UJ-0002fW-Dd for qemu-devel@nongnu.org; Tue, 23 Jun 2009 11:00:47 -0400 Received: from [199.232.76.173] (port=60427 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MJ7UJ-0002fB-62 for qemu-devel@nongnu.org; Tue, 23 Jun 2009 11:00:43 -0400 Received: from mx2.redhat.com ([66.187.237.31]:60228) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MJ7UI-0005if-I0 for qemu-devel@nongnu.org; Tue, 23 Jun 2009 11:00:42 -0400 Message-ID: <4A40EE4C.4020009@redhat.com> Date: Tue, 23 Jun 2009 18:01:32 +0300 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Qemu-devel] Re: [PATCH 01/11] QMP: Introduce specification file References: <20090623012811.53a62493@doriath> <4A40989C.1050805@redhat.com> <4A40D4C1.4040608@codemonkey.ws> <4A40D8F8.4050508@redhat.com> <4A40DB6A.8000106@codemonkey.ws> In-Reply-To: <4A40DB6A.8000106@codemonkey.ws> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: aliguori@us.ibm.com, ehabkost@redhat.com, jan.kiszka@siemens.com, dlaor@redhat.com, qemu-devel@nongnu.org, Luiz Capitulino On 06/23/2009 04:40 PM, Anthony Liguori wrote: >> IMO, there aren't any. All commands are synchronous (but may cause >> events to be generated later). > > > At least today, there are quite a few commands that are synchronous > and block. They would all have to be converted to events. For instance: > That's what I meant, though I phrased it poorly. > commit That's a biggie to make truly async. > change > screendump I think we can keep those synchronous. > savevm > loadvm > delvm Like commit, very difficult to make async. > stop > cont These certainly seem very synchronous to me. > memsave > pmemsave Can keep these synchronous IMO. You certainly don't want the guest to progress during memsave. > migrate > balloon Isn't balloon synchronous? It sets the target and exits immediately. We don't want command completion to depend on the guest. -- error compiling committee.c: too many arguments to function