From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:35968) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UIkBr-0005FP-1w for qemu-devel@nongnu.org; Thu, 21 Mar 2013 14:26:16 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UIkBo-0000oR-QZ for qemu-devel@nongnu.org; Thu, 21 Mar 2013 14:26:14 -0400 Received: from e23smtp07.au.ibm.com ([202.81.31.140]:43551) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UIkBo-0000o6-9P for qemu-devel@nongnu.org; Thu, 21 Mar 2013 14:26:12 -0400 Received: from /spool/local by e23smtp07.au.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Fri, 22 Mar 2013 04:17:46 +1000 Received: from d23relay04.au.ibm.com (d23relay04.au.ibm.com [9.190.234.120]) by d23dlp03.au.ibm.com (Postfix) with ESMTP id 52618357804A for ; Fri, 22 Mar 2013 05:26:02 +1100 (EST) Received: from d23av03.au.ibm.com (d23av03.au.ibm.com [9.190.234.97]) by d23relay04.au.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r2LICEnn6488520 for ; Fri, 22 Mar 2013 05:12:16 +1100 Received: from d23av03.au.ibm.com (loopback [127.0.0.1]) by d23av03.au.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r2LIP8v6018371 for ; Fri, 22 Mar 2013 05:25:08 +1100 From: Anthony Liguori In-Reply-To: <514B1C76.4020400@redhat.com> References: <1363772625-9182-1-git-send-email-kraxel@redhat.com> <1363772625-9182-23-git-send-email-kraxel@redhat.com> <514ABC48.4070606@redhat.com> <514ACA0B.7030706@redhat.com> <514B1C76.4020400@redhat.com> Date: Thu, 21 Mar 2013 13:25:04 -0500 Message-ID: <87ppys6267.fsf@codemonkey.ws> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: [Qemu-devel] [PATCH 22/23] gtk: show a window for each graphical QemuConsole List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gerd Hoffmann , Peter Maydell Cc: qemu-devel@nongnu.org Gerd Hoffmann writes: > Hi, > >>>>> If so, we're going to need to model what the hardware actually >>>>> does, which is that there's a single connection on the back >>>>> of the box for a monitor, and it's guest software controllable >>>>> which of the two display devices is routed to the connection... >>>> >>>> How does this work in 1.4? >>> >>> I guess the second display device was never ever shown anywhere? >> >> Correct. We rely on "last display device wins" plus the fact this >> happens to match up with the device Linux chooses for display. >> This is obviously not great but up til now QEMU hasn't actually >> supported multiple display devices so I haven't worried about it. > > Ok. > > I think the most sensible way to handle this is to implement the output > routing device, make it own the (single) QemuConsole, and depending on > the router state the one or the other display device is allowed to > render to the QemuConsole. Where does the switching happen in hardware? Is this two devices with a DVI port with a switch on it to have a single output port or it is something more sophisticated where there are two memory regions and a register is used to select which one is written out? Regards, Anthony Liguori