From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1LKaZm-0006aL-FN
	for qemu-devel@nongnu.org; Wed, 07 Jan 2009 10:44:10 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1LKaZk-0006ZZ-Si
	for qemu-devel@nongnu.org; Wed, 07 Jan 2009 10:44:09 -0500
Received: from [199.232.76.173] (port=37133 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1LKaZk-0006ZU-JM
	for qemu-devel@nongnu.org; Wed, 07 Jan 2009 10:44:08 -0500
Received: from mx2.suse.de ([195.135.220.15]:38479)
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60)
	(envelope-from <agraf@suse.de>) id 1LKaZk-0000lG-5L
	for qemu-devel@nongnu.org; Wed, 07 Jan 2009 10:44:08 -0500
Received: from Relay2.suse.de (relay-ext.suse.de [195.135.221.8])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mx2.suse.de (Postfix) with ESMTP id A8006484A6
	for <qemu-devel@nongnu.org>; Wed,  7 Jan 2009 16:44:03 +0100 (CET)
Message-ID: <4964CDC2.1080707@suse.de>
Date: Wed, 07 Jan 2009 16:44:02 +0100
From: Alexander Graf <agraf@suse.de>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] [PATCH 1/2] [RFC] Make vmport report the processor
	speed
References: <12976861769-BeMail@laptop>
In-Reply-To: <12976861769-BeMail@laptop>
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: <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

Fran=C3=A7ois Revol wrote:
>>> Do we implement them yet ? grep got me some MSR_IA32_TSC in kvm.c, =20
>>> so I
>>> suppose yes.
>>>      =20
>> That is the TSC value MSR I guess. So no, we don't implement them=20
>> yet. =20
>> But that sounds like a way better interface to me than the VMware =20
>> backdoor ;).
>>    =20
>
> Maybe implementing it properly would fix running ESX without the need=20
> for vmport ?
>  =20

I haven't seen VMware accessing the relevant MSR, so I guess no :-(.

>>> Oh, I didn't notice rdtscp, might be interesting to use instead for
>>> Haiku.
>>>      =20
>> Maybe using a PV clocksource is even better ...
>>    =20
>
> ?
>  =20

Xenner for example uses the KVM_CLOCK to do timings, because the guest
never really knows what time it is. There was a comment on that earlier
in this thread by Avi IIRC too. If you're running virtualized, it's
usually best to use a paravirtualized clocksource.

Alex