From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1NDpBF-0001Uh-TE
	for qemu-devel@nongnu.org; Thu, 26 Nov 2009 19:59:25 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1NDpBA-0001SG-T0
	for qemu-devel@nongnu.org; Thu, 26 Nov 2009 19:59:25 -0500
Received: from [199.232.76.173] (port=48281 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NDpBA-0001SD-NL
	for qemu-devel@nongnu.org; Thu, 26 Nov 2009 19:59:20 -0500
Received: from mx1.redhat.com ([209.132.183.28]:22025)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <lcapitulino@redhat.com>) id 1NDpBA-0004Ng-8B
	for qemu-devel@nongnu.org; Thu, 26 Nov 2009 19:59:20 -0500
From: Luiz Capitulino <lcapitulino@redhat.com>
Date: Thu, 26 Nov 2009 22:58:50 -0200
Message-Id: <1259283550-3597-1-git-send-email-lcapitulino@redhat.com>
Subject: [Qemu-devel] [PATCH v1 00/20] QEMU Monitor Protocol
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org
Cc: aliguori@us.ibm.com, avi@redhat.com, armbru@redhat.com

 Hi,

 This series has a number of improvements over v0 and is a serious
candidate for inclusion.

 Something I'd like to make clear is that QMP is still unstable:
some commands output are being fixed and most of the error handling
has not been done yet.

 It might look scary to have an unstable protocol merged, on the other
hand several issues will only come to light with real people testing
QMP (yeah, I'm not real ;) ).

 I have two solutions for this problem, both assumes QMP is merged:

1. We merge it ASAP and rush to fix its issues until the release
   date

2. We add a compile time switch (eg. --enable-protocol) and disable
   QMP by default

 Now, regarding this series, the biggest visible change is that we now
support 'query-' commands.

 For example, instead of:

{ "execute": "info", "arguments": { "item": "version" } }

 Clients should do:

{ "execute": "query-version" }

 A summarized changelog follows.

changelog
---------

v0 -> v1

- query- commands support
- Better error classes
- Using the stream parser
- Improved patch split
- Several smalls changes and fixes