From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:32975) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UoZtd-0004Qw-QG for qemu-devel@nongnu.org; Mon, 17 Jun 2013 09:56:12 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UoZtB-00064v-1X for qemu-devel@nongnu.org; Mon, 17 Jun 2013 09:55:01 -0400 Received: from mx1.redhat.com ([209.132.183.28]:35785) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UoZtA-00064V-PU for qemu-devel@nongnu.org; Mon, 17 Jun 2013 09:54:32 -0400 Date: Mon, 17 Jun 2013 09:54:30 -0400 From: Luiz Capitulino Message-ID: <20130617095430.0c54df50@redhat.com> In-Reply-To: <51BEA782.7030201@redhat.com> References: <1371151644-22308-1-git-send-email-alevy@redhat.com> <87mwqspn89.fsf@codemonkey.ws> <51BEA782.7030201@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH] make screendump an async command List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gerd Hoffmann Cc: airlied@redhat.com, Anthony Liguori , Alon Levy , qemu-devel@nongnu.org On Mon, 17 Jun 2013 08:06:58 +0200 Gerd Hoffmann wrote: > Hmm, while thinking about it: There is another screendump change in the > pipeline: allow screen dumps from *any* device. So, I think this is > actually a very good reason to implement a new screendump command as I > think we can kill two birds with one stone then: > > First we can add a new parameter to specify the device we want dump > from. And second we are not bound to the behavior of the existing > screendump command. So we could simply send out a qmp event as > completion (or error) notification. That's how we agreed on doing async commands, and looks like a good solution to me.