From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Nd81z-00005x-2n for qemu-devel@nongnu.org; Thu, 04 Feb 2010 15:10:27 -0500 Received: from [199.232.76.173] (port=33039 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Nd81y-00005Y-PA for qemu-devel@nongnu.org; Thu, 04 Feb 2010 15:10:26 -0500 Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1Nd81x-0008Gq-TN for qemu-devel@nongnu.org; Thu, 04 Feb 2010 15:10:26 -0500 Received: from mx1.redhat.com ([209.132.183.28]:2103) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Nd81v-0008GN-CN for qemu-devel@nongnu.org; Thu, 04 Feb 2010 15:10:24 -0500 From: Luiz Capitulino Date: Thu, 4 Feb 2010 18:10:03 -0200 Message-Id: <1265314207-6323-1-git-send-email-lcapitulino@redhat.com> Subject: [Qemu-devel] [PATCH v2 0/4]: QMP capability negotiation support 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 Capability negotiation allows clients to enable new QMP capabilities they support and thus allows QMP to evolve in a compatible way. This series implements Markus's design and is a revamp of the previous one. It's very simple now, as mode-oriented support has been dropped. I've maintained the same terminology, though. Basically, QMP starts in capability negotiation mode where only the 'qmp_capabilities' command is allowed to run. This command should be used by clients to enable capabilities they support. When this command is issued QMP enters in command mode, where the party begins. Details in the patches. changelog --------- v1 -> v2 - Typos and minor changes v0 -> v1 - Drop mode-oriented support