From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Lsibj-0001YP-0p for qemu-devel@nongnu.org; Sat, 11 Apr 2009 15:11:15 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Lsibe-0001Wj-BR for qemu-devel@nongnu.org; Sat, 11 Apr 2009 15:11:14 -0400 Received: from [199.232.76.173] (port=45529 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Lsibe-0001We-8E for qemu-devel@nongnu.org; Sat, 11 Apr 2009 15:11:10 -0400 Received: from mx2.redhat.com ([66.187.237.31]:54296) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Lsibd-0007rv-RE for qemu-devel@nongnu.org; Sat, 11 Apr 2009 15:11:10 -0400 Message-ID: <49E0EB46.3050803@redhat.com> Date: Sat, 11 Apr 2009 22:11:02 +0300 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH 1/6] Allow multiple monitor devices (v2) References: <1239215702-23818-1-git-send-email-aliguori@us.ibm.com> <49DDAF9F.7040400@redhat.com> <49DDF807.1050707@us.ibm.com> <49DDFAD5.7060808@redhat.com> <49DDFC5C.4080504@us.ibm.com> <49DE0042.9050103@redhat.com> <49DE0271.8090103@us.ibm.com> <49DE05F2.5060304@redhat.com> <49DE0673.3070501@us.ibm.com> <49DE081D.1030702@redhat.com> <49DE0CF2.3060307@us.ibm.com> <49DE1029.3030909@redhat.com> <49DE16DE.6030206@us.ibm.com> <49DE1AD2.2060600@redhat.com> <49DE1DB3.30402@us.ibm.com> <49DE229B.7050408@redhat.com> <49DE2580.2030507@us.ibm.com> In-Reply-To: <49DE2580.2030507@us.ibm.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: libvir-list@redhat.com, Jan Kiszka , qemu-devel@nongnu.org, Hollis Blanchard Anthony Liguori wrote: > > What's the established practice? Do you know of any protocol that is > line based that does notifications like this? > Actually there is one line oriented protocol that does asynchronous notifications. http://faqs.org/rfcs/rfc1459.html -- Do not meddle in the internals of kernels, for they are subtle and quick to panic.