From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1EFXU6-0001Ff-4U
	for qemu-devel@nongnu.org; Wed, 14 Sep 2005 09:39:34 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1EFXU0-0001Dg-Mx
	for qemu-devel@nongnu.org; Wed, 14 Sep 2005 09:39:31 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1EFXTz-00019K-Qq
	for qemu-devel@nongnu.org; Wed, 14 Sep 2005 09:39:28 -0400
Received: from [128.8.10.163] (helo=po1.wam.umd.edu)
	by monty-python.gnu.org with esmtp (Exim 4.34) id 1EFXTz-0006h6-8F
	for qemu-devel@nongnu.org; Wed, 14 Sep 2005 09:39:27 -0400
Received: from jbrown.mylinuxbox.org (jma-box.student.umd.edu [129.2.253.219])
	by po1.wam.umd.edu (8.12.10/8.12.10) with ESMTP id j8EDdQxA018449
	for <qemu-devel@nongnu.org>; Wed, 14 Sep 2005 09:39:26 -0400 (EDT)
Date: Wed, 14 Sep 2005 09:39:21 -0400
From: "Jim C. Brown" <jma5@umd.edu>
Subject: Re: [Qemu-devel] About qemu emulation speed (a question) and
	supported OS
Message-ID: <20050914133921.GB6052@jbrown.mylinuxbox.org>
References: <1dc7f0e3050913053635cd61af@mail.gmail.com>
	<20050913214856.GA31111@jbrown.mylinuxbox.org>
	<43278F61.8060103@us.ibm.com>
	<200509140448.24354.mark.williamson@cl.cam.ac.uk>
	<4327A6BB.1040509@us.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4327A6BB.1040509@us.ibm.com>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

On Tue, Sep 13, 2005 at 11:27:39PM -0500, Anthony Liguori wrote:
> I reckon kqemu has this same problem... Technically, even in ring 3, if 
> you run natively, you violate the Popek/Goldberg requirements because of 
> cpuid.  It's just not possible to trap it but it shouldn't matter for 
> most software.
> 

It is possible to trap it, in a sense. You just read ahead and replace the
cpuid instruction with something else.

Ugly, but doable.

-- 
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.