From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D0UXR-0003Bo-GB for qemu-devel@nongnu.org; Sun, 13 Feb 2005 19:56:33 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D0UXB-00032t-5w for qemu-devel@nongnu.org; Sun, 13 Feb 2005 19:56:18 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D0UXA-00030G-UN for qemu-devel@nongnu.org; Sun, 13 Feb 2005 19:56:17 -0500 Received: from [128.8.10.162] (helo=po0.wam.umd.edu) by monty-python.gnu.org with esmtp (Exim 4.34) id 1D0UF8-0003NJ-4Y for qemu-devel@nongnu.org; Sun, 13 Feb 2005 19:37:38 -0500 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 j1E0bbnX007073 for ; Sun, 13 Feb 2005 19:37:37 -0500 (EST) Date: Sun, 13 Feb 2005 19:37:37 -0500 From: "Jim C. Brown" Subject: Re: [Qemu-devel] coLinux and Qemu? --was-- Plex86 and Qemu Message-ID: <20050214003737.GB31421@jbrown.mylinuxbox.org> References: <20050213182734.GA29432@jbrown.mylinuxbox.org> <001c01c51203$24d2e510$254d21d1@computername> <20050213220614.GA30662@jbrown.mylinuxbox.org> <000e01c51222$8f893890$254d21d1@computername> <1108339538.1601.5.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1108339538.1601.5.camel@localhost.localdomain> 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, Feb 14, 2005 at 01:05:38PM +1300, Darryl Dixon wrote: > Just a thought, but coLinux (www.colinux.org) has a low-level Windows > driver to give the Linux kernel access to the CPU. Perhaps this could > be modified to simply allow Qemu to execute user-space code (a la kqemu) > on Windows? I wasn't aware that CoLinux did this (or that it even needed to). I am not sure how CoLinux works - whether or not this is possible depends on how CoLinux runs linux executables (i.e. whether or not they need to be virtalized). If it does do virtalization, this should be a viable approach. -- Infinite complexity begets infinite beauty. Infinite precision begets infinite perfection.