From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=39454 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OwKxG-0000PB-Ph for qemu-devel@nongnu.org; Thu, 16 Sep 2010 16:21:16 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OwKxF-0001Mg-6m for qemu-devel@nongnu.org; Thu, 16 Sep 2010 16:21:14 -0400 Received: from mx1.redhat.com ([209.132.183.28]:21465) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OwKxE-0001MW-Vy for qemu-devel@nongnu.org; Thu, 16 Sep 2010 16:21:13 -0400 From: Luiz Capitulino Date: Thu, 16 Sep 2010 17:20:46 -0300 Message-Id: <1284668464-15981-1-git-send-email-lcapitulino@redhat.com> Subject: [Qemu-devel] [PATCH 00/18] Monitor: split HMP and QMP dispatch tables List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: aliguori@us.ibm.com, armbru@redhat.com The subject says it all: with this series applied we'll get different dispatch tables for HMP and QMP, which has the side effect of making QMP commands (such as qmp_capabilities) disappear from HMP's scope. This is also the beginning of the Monitor's redesign, which aims to separate QMP, HMP and common code. There's a penalty, though. We're going to get a bit of duplication during the process, like duplicated handlers entries in the dispatch tables. We'll need more separation and a proper internal QMP interface to solve that... --- Makefile | 2 +- Makefile.target | 7 +- monitor.c | 357 ++++++++----- monitor.h | 1 - qemu-monitor-qmp.hx | 1541 +++++++++++++++++++++++++++++++++++++++++++++++++++ qemu-monitor.hx | 1361 +--------------------------------------------- 6 files changed, 1774 insertions(+), 1495 deletions(-)