From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MY0rT-0005tD-OW
	for qemu-devel@nongnu.org; Mon, 03 Aug 2009 12:58:11 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MY0rO-0005qY-V8
	for qemu-devel@nongnu.org; Mon, 03 Aug 2009 12:58:11 -0400
Received: from [199.232.76.173] (port=55268 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MY0rO-0005qM-OV
	for qemu-devel@nongnu.org; Mon, 03 Aug 2009 12:58:06 -0400
Received: from mx2.redhat.com ([66.187.237.31]:56272)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <lcapitulino@redhat.com>) id 1MY0rO-00036o-6m
	for qemu-devel@nongnu.org; Mon, 03 Aug 2009 12:58:06 -0400
From: Luiz Capitulino <lcapitulino@redhat.com>
Date: Mon,  3 Aug 2009 13:56:57 -0300
Message-Id: <1249318642-19324-1-git-send-email-lcapitulino@redhat.com>
Subject: [Qemu-devel] [PATCH v1 00/25] Monitor handlers new structure phase 1
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: jan.kiszka@siemens.com, aliguori@us.ibm.com, avi@redhat.com

 Hi there,

 In the long QEMU Monitor Protocol (QMP) thread people have agreed that,
whichever protocol we are going to use, the first step that needs to be
done is to improve current Monitor's code, so that command handlers
support 'structured' input and output.

 Basically, this means that handlers will receive their input through
a dictionary (instead of the ugly args[] array) and will output their
data back to the Monitor instead of directly printing them.

 Once this is done, plugging the protocol should be simple, as handlers
will be part of the common code, working with both the human and (any)
machine protocols.

 I have divided this project in the following phases:

 1. Command handlers receive their arguments through a dictionary
 2. Create a object model for QEMU
 3. Command handlers output their data back to the Monitor
 4. Plug the protocol

 This patchset implements phase 1.

Changelog:

V0 -> V1

- Fix C standard violations
- Various renames (QDict, QDictEntry, etc)
- Remove qemu_ prefix from functions
- Drop qdict_iter() (unused right now)
- Fix some unneeded int to long type changes