From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=56344 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1PVsYf-0004bt-SE
	for qemu-devel@nongnu.org; Thu, 23 Dec 2010 16:18:46 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <stefboombastic@gmail.com>) id 1PVsYf-0005yK-43
	for qemu-devel@nongnu.org; Thu, 23 Dec 2010 16:18:45 -0500
Received: from mail-ww0-f41.google.com ([74.125.82.41]:36027)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <stefboombastic@gmail.com>) id 1PVsYe-0005yD-Vx
	for qemu-devel@nongnu.org; Thu, 23 Dec 2010 16:18:45 -0500
Received: by wwi18 with SMTP id 18so6617323wwi.4
	for <qemu-devel@nongnu.org>; Thu, 23 Dec 2010 13:18:44 -0800 (PST)
Message-ID: <4D13BCB1.6030206@gmail.com>
Date: Thu, 23 Dec 2010 22:18:41 +0100
From: Stefano Bonifazi <stefboombastic@gmail.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] checking the number of target cpu cycles or
	instructions executed
References: <4D11ECE8.4050903@gmail.com>
	<71276548-B635-4B30-9660-4F61F6930452@web.de>
In-Reply-To: <71276548-B635-4B30-9660-4F61F6930452@web.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
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.nongnu.org/archive/html/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: =?ISO-8859-1?Q?Andreas_F=E4rber?= <andreas.faerber@web.de>
Cc: QEMU Developers <qemu-devel@nongnu.org>

On 12/23/2010 06:42 PM, Andreas Färber wrote:
> Hi,
>
> Am 22.12.2010 um 13:19 schrieb Stefano Bonifazi:
>
>> how can I check the number of target cpu cycles or target 
>> instructions executed inside qemu-user (i.e. qemu-ppc)?
>> Is there any variable I can inspect for such informations?
>
> QEMU's emulation is not cycle-accurate, so you will not be able to 
> retrieve CPU cycle info to my knowledge.
>
> As for instructions, take a look at the -icount option.
>
> Andreas
Hi!
  Thank You very much! I understood it was not a cycle accurate 
emulator.. In my case I am more interested in how many instructions the 
target machine would execute rather than how many host cycles or 
instructions..so I think counted fetched target instructions can be good..
Anyway how to switch on -icount option for user emulation? Setting 
use_icount to 1 (or2) into exec.c does not work: the execution hangs, 
and qemu_icount is not incremented..
Thank you!
Best Regards,
Stefano B.