From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DLopY-0007Ed-T5 for qemu-devel@nongnu.org; Wed, 13 Apr 2005 16:51:25 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DLopV-0007BW-UM for qemu-devel@nongnu.org; Wed, 13 Apr 2005 16:51:23 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DLonM-0005sV-9X for qemu-devel@nongnu.org; Wed, 13 Apr 2005 16:49:08 -0400 Received: from [128.8.10.162] (helo=po0.wam.umd.edu) by monty-python.gnu.org with esmtp (Exim 4.34) id 1DLpA5-0004ag-7m for qemu-devel@nongnu.org; Wed, 13 Apr 2005 17:12:37 -0400 Received: from jbrown.mylinuxbox.org (jma-box.student.umd.edu [129.2.237.180]) by po0.wam.umd.edu (8.12.10/8.12.10) with ESMTP id j3DLC5ud004678 for ; Wed, 13 Apr 2005 17:12:05 -0400 (EDT) Date: Wed, 13 Apr 2005 17:12:04 -0400 From: "Jim C. Brown" Subject: Re: [Qemu-devel] qvm86, kqemu and video speed Message-ID: <20050413211204.GA23439@jbrown.mylinuxbox.org> References: <425A84B0.60200@praguespringpeople.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <425A84B0.60200@praguespringpeople.org> 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 On Mon, Apr 11, 2005 at 04:07:44PM +0200, Struan Bartlett wrote: > I understand qvm86 and kqemu provide some virtualisation of the host > machine, including allowing the guest some direct memory access. Is it > conceivable for these modules to be extended to allow the guest machine > to directly write to host video memory, or else to a host memory buffer > that is copied into the Qemu window? > This is doable, however I personally think that it is better to keep this all userspace. Even for fast 3d graphics, you dnt have to use kernel mechanisms, you could get away with using a custom videocard (or careful emulation of an existing 3d card) and mapping it to, say, OpenGL calls. Most optimizations can be done in userspace. There was a patch sent a while back (the pci-proxy patch) that in theory would allow qemu guest to use a host PCI video card (such as a PCI Voodoo3 card). This was never actually tested, and I don't remeber if this patch has been updated to work against the current version of qemu. -- Infinite complexity begets infinite beauty. Infinite precision begets infinite perfection.