From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LPGDS-0000IT-KQ for qemu-devel@nongnu.org; Tue, 20 Jan 2009 08:00:26 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LPGDQ-0000HJ-Ss for qemu-devel@nongnu.org; Tue, 20 Jan 2009 08:00:26 -0500 Received: from [199.232.76.173] (port=60176 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LPGDQ-0000HE-J1 for qemu-devel@nongnu.org; Tue, 20 Jan 2009 08:00:24 -0500 Received: from lizzard.sbs.de ([194.138.37.39]:23964) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LPGDO-0004tN-Pn for qemu-devel@nongnu.org; Tue, 20 Jan 2009 08:00:23 -0500 Received: from mail2.sbs.de (localhost [127.0.0.1]) by lizzard.sbs.de (8.12.11.20060308/8.12.11) with ESMTP id n0KD0Je2010318 for ; Tue, 20 Jan 2009 14:00:19 +0100 Received: from [139.25.109.167] (mchn012c.ww002.siemens.net [139.25.109.167] (may be forged)) by mail2.sbs.de (8.12.11.20060308/8.12.11) with ESMTP id n0KD0J17010990 for ; Tue, 20 Jan 2009 14:00:19 +0100 Message-ID: <4975CAE8.6040700@siemens.com> Date: Tue, 20 Jan 2009 14:00:24 +0100 From: Jan Kiszka MIME-Version: 1.0 References: <4975A853.5080603@siemens.com> In-Reply-To: <4975A853.5080603@siemens.com> Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: Multiple monitor terminals 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 Jan Kiszka wrote: > Hi, > > trying to re-animate Jason Wessel's nice monitor-pass-through patches > for the gdbstub that we carry in our tree, I'm currently a bit lost in > the monitor mux design. Why do we need multiple monitor terminal devices > at the moment? And why are they all receiving the same output? What > would be a scenario for more than one monitor_hd != NULL? To answer myself: The idea seems to be allowing to mux the monitor on other character devices, be it one or more, be there also a dedicated monitor terminal at the same time. But I still wonder if it is a desirable behavior to have this broadcasting of typed commands and their replies. Thinking more about this now. > > Jason once suggested to define a focus when issuing a new command and > send all related replies only back to this focused terminal. I think > this would fit quite well for most use cases, specifically when adding > another monitor channel via remote gdb. Just migration raises some > concerns ATM. But as I may oversee more issues while trying to apply > this focus concept also on the existing monitor terminals, I'd like to > get some feedback on this approach first. > > Thanks in advance, > Jan > Jan -- Siemens AG, Corporate Technology, CT SE 2 Corporate Competence Center Embedded Linux