From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mqnh2-0002rR-O8 for qemu-devel@nongnu.org; Thu, 24 Sep 2009 08:45:04 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mqngx-0002pl-Mi for qemu-devel@nongnu.org; Thu, 24 Sep 2009 08:45:04 -0400 Received: from [199.232.76.173] (port=50601 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mqngx-0002pI-0Z for qemu-devel@nongnu.org; Thu, 24 Sep 2009 08:44:59 -0400 Received: from mx1.redhat.com ([209.132.183.28]:47515) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mqngw-0001xy-Jj for qemu-devel@nongnu.org; Thu, 24 Sep 2009 08:44:58 -0400 Message-ID: <4ABB69C0.1000404@redhat.com> Date: Thu, 24 Sep 2009 15:44:48 +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> In-Reply-To: <20090924093146.66191c37@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 03:31 PM, Luiz Capitulino wrote: > >> What about capability negotiation? Server offers capabilities, client >> can accept or decline them. >> >> [...] >> > 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. -- Do not meddle in the internals of kernels, for they are subtle and quick to panic.