From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1HdZIp-00028Z-GO
	for qemu-devel@nongnu.org; Mon, 16 Apr 2007 18:04:03 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1HdZIm-00026T-D3
	for qemu-devel@nongnu.org; Mon, 16 Apr 2007 18:04:03 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1HdZIm-00026Q-7y
	for qemu-devel@nongnu.org; Mon, 16 Apr 2007 18:04:00 -0400
Received: from nz-out-0506.google.com ([64.233.162.225])
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <edusaper@gmail.com>) id 1HdZE7-0000jE-3w
	for qemu-devel@nongnu.org; Mon, 16 Apr 2007 17:59:11 -0400
Received: by nz-out-0506.google.com with SMTP id i11so3224361nzi
	for <qemu-devel@nongnu.org>; Mon, 16 Apr 2007 14:59:10 -0700 (PDT)
Message-ID: <83a4d4ca0704161459g45e5988fmabf3ea8f3fe26e64@mail.gmail.com>
Date: Mon, 16 Apr 2007 23:59:09 +0200
From: "Eduardo Felipe" <edusaper@gmail.com>
Subject: Re: [Qemu-devel] time inside qemu
In-Reply-To: <45955621.2030301@uab.cat>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_60064_5350174.1176760749658"
References: <459540A8.8020209@uab.cat>
	<200612291743.05983.paul@codesourcery.com> <45955621.2030301@uab.cat>
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

------=_Part_60064_5350174.1176760749658
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi,

> I just tried with cpu_disable_ticks() and cpu_enable_ticks(). It seems to
> work partially: at least now system date and time are out of sync..
>

Maybe a more accurate way to do this is mimicking "stop" and "continue"
monitor commands:

vm_stop(EXCP_INTERRUPT);
[SystemC simulation]
vm_start();

This just takes SystemC emulation time out of the equation. You cannot make
any reliable performance measure of qemu's translated code, as already
mentioned, but the former may be enough for your requirements.

Regards,
Eduardo Felipe

------=_Part_60064_5350174.1176760749658
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi,&nbsp;<div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div bgcolor="#ffffff" text="#000000">
I just tried with cpu_disable_ticks() and cpu_enable_ticks(). It seems
to work partially: at least now system date and time are out of sync..</div></blockquote><div><br>Maybe a more accurate way to do this is mimicking &quot;stop&quot; and &quot;continue&quot; monitor commands:<br><br>vm_stop(EXCP_INTERRUPT);
<br>[SystemC simulation]<br>vm_start();<br><br>This just takes SystemC emulation time out of the equation. You cannot make any reliable performance measure of qemu&#39;s translated code, as already mentioned, but the former may be enough for your requirements.
<br><br>Regards,<br>Eduardo Felipe<br></div></div><br>

------=_Part_60064_5350174.1176760749658--