From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1EYvOm-0005jU-03 for qemu-devel@nongnu.org; Sun, 06 Nov 2005 20:02:12 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1EYvOk-0005iM-9o for qemu-devel@nongnu.org; Sun, 06 Nov 2005 20:02:11 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EYvOk-0005iJ-6p for qemu-devel@nongnu.org; Sun, 06 Nov 2005 20:02:10 -0500 Received: from [32.97.110.150] (helo=e32.co.us.ibm.com) by monty-python.gnu.org with esmtp (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA:24) (Exim 4.34) id 1EYvOj-0002XW-Ss for qemu-devel@nongnu.org; Sun, 06 Nov 2005 20:02:10 -0500 Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com [9.17.195.106]) by e32.co.us.ibm.com (8.12.11/8.12.11) with ESMTP id jA7128nX013798 for ; Sun, 6 Nov 2005 20:02:08 -0500 Received: from d03av01.boulder.ibm.com (d03av01.boulder.ibm.com [9.17.195.167]) by d03relay04.boulder.ibm.com (8.12.10/NCO/VERS6.8) with ESMTP id jA713Hqf064352 for ; Sun, 6 Nov 2005 18:03:17 -0700 Received: from d03av01.boulder.ibm.com (loopback [127.0.0.1]) by d03av01.boulder.ibm.com (8.12.11/8.13.3) with ESMTP id jA7128W2001237 for ; Sun, 6 Nov 2005 18:02:08 -0700 Message-ID: <436EA787.5040503@us.ibm.com> Date: Sun, 06 Nov 2005 19:01:59 -0600 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] Qemu and (Pacifica | Vanderpool) References: <200511061019.18720.dfeustel@verizon.net> <200511061533.13098.paul@codesourcery.com> <200511061616.25284.mark.williamson@cl.cam.ac.uk> In-Reply-To: <200511061616.25284.mark.williamson@cl.cam.ac.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: Paul Brook Mark Williamson wrote: >>qemu is an emulator, not a virtualizer, so these extensions don't really >>help. >> >> > >They could be leveraged by kqemu one day... > >/me thinks we'll see a rash of Linux kernel "hypervisor modules" when VTX / >SVM hardware is available. > > Indeed. I've already started my own ;-) My initial guess is that the kqemu/qvm86 model would work quite well extended for VT/SVM. That is, a kernel driver that provides a memory area that can be read-from/written-to in userspace, and then an ioctl interface that blocks while running code and returns when a sensitive instruction is hit. It probably makes sense to handle most of the stuff in kernel space (shadow paging and such) and just return to userspace for IO operations. Regards, Anthony Liguori >Cheers, >Mark > > > >>You may want to look at Xen (www.xensource.com), which already supports >>these. >> >>Paul >> >> >>_______________________________________________ >>Qemu-devel mailing list >>Qemu-devel@nongnu.org >>http://lists.nongnu.org/mailman/listinfo/qemu-devel >> >> > > >_______________________________________________ >Qemu-devel mailing list >Qemu-devel@nongnu.org >http://lists.nongnu.org/mailman/listinfo/qemu-devel > > >