From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=58401 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Px6B0-00046m-3g for qemu-devel@nongnu.org; Tue, 08 Mar 2011 18:18:51 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Px6Ay-0004yD-Sm for qemu-devel@nongnu.org; Tue, 08 Mar 2011 18:18:49 -0500 Received: from mx1.redhat.com ([209.132.183.28]:38832) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Px6Ay-0004xm-Gi for qemu-devel@nongnu.org; Tue, 08 Mar 2011 18:18:48 -0500 Date: Tue, 8 Mar 2011 20:18:42 -0300 From: Luiz Capitulino Message-ID: <20110308201842.73ba7a19@doriath> In-Reply-To: <4D73F49D.9010001@codemonkey.ws> References: <4D73F49D.9010001@codemonkey.ws> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: QAPI Merge Plans List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: qemu-devel , Markus Armbruster On Sun, 06 Mar 2011 14:54:53 -0600 Anthony Liguori wrote: > Hi, > > I've gotten my QAPI branch now functionally complete so I'm ready to > start working on merging. I thought I'd send a note about my plans as > both a heads up and to see if anyone had any suggestions. > > My plan is to split everything up into three rounds. The first round > will just be core infrastructure--the code generator, the new QMP > server, the signal infrastructure, etc. This round will introduce a new > command line option to expose the new QMP server (still chardev based). This means current-to-be-replaced infrastructure is still available? I'd like to avoid having two (public) QMPs if possible, even temporary. Btw, I've been maintaining a QMP tree but as this is a whole new thing, I think that this can be directly merged on master as soon as you get the (whatever needed) ACKs. > > Round two will consist of all of the 0.14 commands. Some new commands > are also needed because some of the 0.14 commands are untestable without > new QMP commands :-/ > > Finally, round three will include some of the new and potentially > controversial bits like the new non-chardev based QMP server, default > session and discovery, qsh tool, etc. > > After these three rounds are merged, I'll then work on adding all of the > new QMP commands to support a full HMP session. > > I've tried to put a ton of information on the wiki that hopefully will > give a good amount of background along with current status. > > I expect the first round of patches to be on list this week. > > http://wiki.qemu.org/Features/QAPI > > Regards, > > Anthony Liguori >