From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1LZrBq-00069r-T6
	for qemu-devel@nongnu.org; Wed, 18 Feb 2009 13:30:34 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1LZrBp-00069e-LF
	for qemu-devel@nongnu.org; Wed, 18 Feb 2009 13:30:34 -0500
Received: from [199.232.76.173] (port=51867 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1LZrBp-00069b-Fj
	for qemu-devel@nongnu.org; Wed, 18 Feb 2009 13:30:33 -0500
Received: from csl.cornell.edu ([128.84.224.10]:2566 helo=vlsi.csl.cornell.edu)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <vince@stanley.csl.cornell.edu>) id 1LZrBp-0003up-7a
	for qemu-devel@nongnu.org; Wed, 18 Feb 2009 13:30:33 -0500
Received: from stanley.csl.cornell.edu (stanley.csl.cornell.edu
	[128.84.224.15])
	by vlsi.csl.cornell.edu (8.13.4/8.13.4) with ESMTP id n1IIUR2c082542
	for <qemu-devel@nongnu.org>; Wed, 18 Feb 2009 13:30:32 -0500 (EST)
Date: Wed, 18 Feb 2009 13:30:27 -0500 (EST)
From: Vince Weaver <vince@csl.cornell.edu>
Subject: Re: [Qemu-devel] Monitor Memory Accesses
In-Reply-To: <499C38F3.9050204@gmail.com>
Message-ID: <20090218132622.U28170@stanley.csl.cornell.edu>
References: <499C03A9.6040003@gmail.com>
	<761ea48b0902180500wbe676d4x3895d37df10e495b@mail.gmail.com>
	<499C0A81.8090106@gmail.com>
	<761ea48b0902180526q1be52725x748c7c14b5d907de@mail.gmail.com>
	<499C2BEF.6010107@gmail.com>
	<761ea48b0902180752p2e665a07vbb922fb6621a7173@mail.gmail.com>
	<20090218111027.D27797@stanley.csl.cornell.edu>
	<499C38F3.9050204@gmail.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
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 Wed, 18 Feb 2009, Andrea Pellegrini wrote:
> nice to talk to you again. I figured that we are trying to do basically the 
> same thing. Are you able to use the traces from Qemu with Dinero? If so, in 
> case of cache miss, can you stall the execution of Qemu for some cycles?

You can use Qemu to generate traces for Dinero, patches for that were 
previously mentioned in this thread.

Stalling is meaningless though... Qemu is not cycle-accurate.

If you really want cycle accurate values, you're going to have to feed the 
traces from Qemu into a timing simulator.  It might be possible to create 
a simple mips timing simulator that hooks into Qemu (see my wddd 2008 
paper) but that would involve significant hacking that's not really 
related to Qemu development.

Vince