From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LPIWR-0008DS-P8 for qemu-devel@nongnu.org; Tue, 20 Jan 2009 10:28:11 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LPIWO-0008C5-98 for qemu-devel@nongnu.org; Tue, 20 Jan 2009 10:28:11 -0500 Received: from [199.232.76.173] (port=40821 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LPIWN-0008By-Vw for qemu-devel@nongnu.org; Tue, 20 Jan 2009 10:28:08 -0500 Received: from lizzard.sbs.de ([194.138.37.39]:20019) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LPIWM-00073u-QU for qemu-devel@nongnu.org; Tue, 20 Jan 2009 10:28:07 -0500 Message-ID: <4975ED6F.2060501@siemens.com> Date: Tue, 20 Jan 2009 16:27:43 +0100 From: Jan Kiszka MIME-Version: 1.0 References: <1232448066-32209-1-git-send-email-amit.shah@redhat.com> <4975B6FB.6080302@siemens.com> <20090120133228.GA1891@amit-x200.pnq.redhat.com> In-Reply-To: <20090120133228.GA1891@amit-x200.pnq.redhat.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: [PATCH 1/2] Print asynchronous notifications on request Reply-To: qemu-devel@nongnu.org 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 Amit Shah wrote: > On (Tue) Jan 20 2009 [12:35:23], Jan Kiszka wrote: >> Amit Shah wrote: >>> This patch adds the ability to selectively enable asynchronous notifications >>> from individual qemu subsystems by a new 'notify' monitor command. >>> >>> This is helpful for programs currently parsing monitor output. >>> >>> A sample invocation will look like this: >>> >>> (qemu) >>> >>> (qemu) notify vnc on >>> >>> (qemu) # VNC: Closing down connection 127.0.0.1:1 >>> >>> Notice that the output is prefixed by '#'. Also, it will appear on the >>> line that has '(qemu) ' already output on it. >> I understand the need, but the result looks a bit ugly, at least to >> humans forced to parse it. If you get this while in the middle of type a >> command... Moreover, is it impossible that such an async notification is >> issued while some other subsystem is already dumping a multi-line >> message to the monitor (using multiple prints)? That would be really >> problematic. > > Agreed. However, note that the messages sent via term_printf_async() > will only be emitted if 'notify on' is issued. Humans wouldn't > normally do that. > The scenario I have in mind is a qemu instance managed by libvirt etc. + a monitor console or some forwarded monitor accedd to a gdb frontend used to analyse/debug a guest. On the latter interface, the user may not want to get disturbed by notifications the management tools likes to receive. Jan -- Siemens AG, Corporate Technology, CT SE 2 Corporate Competence Center Embedded Linux