From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KcVOo-0002X3-H6 for qemu-devel@nongnu.org; Sun, 07 Sep 2008 21:18:38 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KcVOo-0002W0-2v for qemu-devel@nongnu.org; Sun, 07 Sep 2008 21:18:38 -0400 Received: from [199.232.76.173] (port=34173 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KcVOn-0002Vr-C1 for qemu-devel@nongnu.org; Sun, 07 Sep 2008 21:18:37 -0400 Received: from mail2.shareable.org ([80.68.89.115]:54735) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1KcVOn-0002zk-4R for qemu-devel@nongnu.org; Sun, 07 Sep 2008 21:18:37 -0400 Date: Mon, 8 Sep 2008 02:18:34 +0100 From: Jamie Lokier Subject: Re: [Qemu-devel] [PATCH] opengl rendering in the sdl window Message-ID: <20080908011833.GA15521@shareable.org> References: <48B81423.9050502@eu.citrix.com> <20080906232723.GB813@shareable.org> <20080907142236.GD4307@implementation> <200809071536.51498.paul@codesourcery.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <200809071536.51498.paul@codesourcery.com> 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: Samuel Thibault Paul Brook wrote: > On Sunday 07 September 2008, Samuel Thibault wrote: > > Jamie Lokier, le Sun 07 Sep 2008 00:27:23 +0100, a écrit : > > > Samuel Thibault wrote: > > > > Jamie Lokier, le Fri 05 Sep 2008 13:02:15 +0100, a écrit : > > > > > Another way to map guest framebuffer to video memory is the XF86DGA > > > > > extension, which is great when you can use it. > > > > > > > > It is being deprecated and probably never works nowadays anyway :) > > > > > > That's a shame as the alternatives are all slower on old video cards. > > > > Yes, and because alternatives don't provide so much performance. > > Ideally, once switched to fullscreen you could just let the guest > > directly write to the actual video memory (particularly interesting for > > Xen and KVM). > > You really don't want to have the guest writing directly to host video ram. > Video ram tends to be high-latency, so you want to write to regular memory, > then use a wide block transfer or DMA to copy to video ram. Latency applies mainly when reading. A good quality guest _expects_ that reading its video RAM will be slow, and only writes to its video RAM, and possible by preparing images off-screen then wide block transfers. :-) > If you really need zero-copy then you should have the renderer read the data > directly out of the guest framebuffer. That still forces one extra copy compared with XF86DGA. "Renderer reads the data directly out of the guest framebuffer" is the extra copy. It's negligable on modern 3d cards, but slow on machines or those where fast blitting or 3d isn't supported. -- Jamie