From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LKWYP-0000MY-7y for qemu-devel@nongnu.org; Wed, 07 Jan 2009 06:26:29 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LKWYN-0000MD-8t for qemu-devel@nongnu.org; Wed, 07 Jan 2009 06:26:28 -0500 Received: from [199.232.76.173] (port=39166 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LKWYN-0000MA-4R for qemu-devel@nongnu.org; Wed, 07 Jan 2009 06:26:27 -0500 Received: from smtp3-g21.free.fr ([212.27.42.3]:35709) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LKWYL-000623-Tr for qemu-devel@nongnu.org; Wed, 07 Jan 2009 06:26:26 -0500 Received: from smtp3-g21.free.fr (localhost [127.0.0.1]) by smtp3-g21.free.fr (Postfix) with ESMTP id A4B3D8181F9 for ; Wed, 7 Jan 2009 12:26:19 +0100 (CET) Received: from laptop (vaf26-2-82-244-111-82.fbx.proxad.net [82.244.111.82]) by smtp3-g21.free.fr (Postfix) with ESMTP id BCE6181812A for ; Wed, 7 Jan 2009 12:26:16 +0100 (CET) In-Reply-To: <1B877137-D03B-414F-857B-3CD28E6DBCF7@suse.de> Subject: Re: [Qemu-devel] [PATCH 1/2] [RFC] Make vmport report the =?utf-8?q?processor_speed?= From: "=?utf-8?q?Fran=C3=A7ois?= Revol" Date: Wed, 07 Jan 2009 12:32:26 +0100 CET Message-Id: <1238254368-BeMail@laptop> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable 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 > >> I don't think doing vmware esx in qemu in vmware us that much of a > >> valid scenario right now ;). > >> > >> But I agree with anthony here - not telling vmware esx that it's > >> running virtualized might be the best. > >> > > > > As I said, it would not only benefit esx. > > Haiku also would likely work much better this way, and possibly > > BeOS > > with a small driver to recalibrate it (I already rewrote such a > > driver > > once, but it was just forcing it using a value from some settings > > that > > were to be taken from a real machine). > > If you really need to get the TSC speed, it might be best to use > official MSRs for that. The Intel documentation definitely includes > such an MSR. Oh, right then, more portable... though I wonder how they work with speedstep... Do we implement them yet =3F grep got me some MSR=5FIA32=5FTSC in kvm.c, so I suppose yes. Oh, I didn't notice rdtscp, might be interesting to use instead for Haiku. Fran=C3=A7ois.