From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mqo2v-0005jM-M8 for qemu-devel@nongnu.org; Thu, 24 Sep 2009 09:07:41 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mqo2q-0005im-7o for qemu-devel@nongnu.org; Thu, 24 Sep 2009 09:07:41 -0400 Received: from [199.232.76.173] (port=38758 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mqo2p-0005ii-VL for qemu-devel@nongnu.org; Thu, 24 Sep 2009 09:07:36 -0400 Received: from mx1.redhat.com ([209.132.183.28]:2461) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mqo2p-0006EM-FB for qemu-devel@nongnu.org; Thu, 24 Sep 2009 09:07:35 -0400 Message-ID: <4ABB6F10.4080608@redhat.com> Date: Thu, 24 Sep 2009 16:07:28 +0300 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Qemu-devel] ANN: QEMU Monitor Protocol git tree References: <20090921224430.610da97b@doriath> <87my4l1e4e.fsf@pike.pond.sub.org> <20090924093146.66191c37@doriath> <4ABB69C0.1000404@redhat.com> <20090924100559.07959a7c@doriath> In-Reply-To: <20090924100559.07959a7c@doriath> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Luiz Capitulino Cc: aliguori@us.ibm.com, Markus Armbruster , qemu-devel@nongnu.org On 09/24/2009 04:05 PM, Luiz Capitulino wrote: >>> I think the easiest way to have this would be to add a >>> monitor command to disable capabilities. Like a command to >>> disable async messages. >>> >>> >> Other way around, enable things that you want. >> > Ok, I will add support for this in my tree then, async messages > will be considered a capability. > Actually, if async messages are specified from day one they can be always active. The client can easily ignore them. -- Do not meddle in the internals of kernels, for they are subtle and quick to panic.