From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1EFay5-0001Xk-H3 for qemu-devel@nongnu.org; Wed, 14 Sep 2005 13:22:46 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1EFaxm-0001On-SR for qemu-devel@nongnu.org; Wed, 14 Sep 2005 13:22:28 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EFaxm-0001O3-ID for qemu-devel@nongnu.org; Wed, 14 Sep 2005 13:22:26 -0400 Received: from [69.17.117.23] (helo=mail21.sea5.speakeasy.net) by monty-python.gnu.org with esmtp (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA:24) (Exim 4.34) id 1EFavz-00022H-Jl for qemu-devel@nongnu.org; Wed, 14 Sep 2005 13:20:35 -0400 Received: from dsl081-088-222.lax1.dsl.speakeasy.net (HELO [192.168.111.2]) ([64.81.88.222]) (envelope-sender ) by mail21.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 14 Sep 2005 17:17:47 -0000 Subject: Re: [Qemu-devel] About qemu emulation speed (a question) and supported OS From: "John R. Hogerhuis" In-Reply-To: <20050914133733.GA6052@jbrown.mylinuxbox.org> References: <1dc7f0e3050913053635cd61af@mail.gmail.com> <20050913133813.GA28356@jbrown.mylinuxbox.org> <4326E903.7070900@us.ibm.com> <20050913214856.GA31111@jbrown.mylinuxbox.org> <43278F61.8060103@us.ibm.com> <20050914133733.GA6052@jbrown.mylinuxbox.org> Content-Type: text/plain Date: Wed, 14 Sep 2005 10:18:24 -0700 Message-Id: <1126718304.24190.126.camel@aragorn> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Reply-To: jhoger@pobox.com, 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 Wed, 2005-09-14 at 09:37 -0400, Jim C. Brown wrote: > VMware handles kernel code. You are right that x86 code can't be 100% virtualized > (even at the userland level) but VMware uses a lot of nasty disgusting tricks > in order to work around them. (For example, playing with shadow pagetables > so that a page of modified code is run but if the code tries to inspect itself > it sees another (unexecuted) page that contains the original code.) > Why disgusting? Seems like a smart implementation given the options at hand. Perhaps you meant disgusting because the Intel architecture forces a virtualizer to handle a bunch of corner cases like this. -- John.