From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MHNb5-0003nB-4K for qemu-devel@nongnu.org; Thu, 18 Jun 2009 15:48:31 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MHNb0-0003lG-EQ for qemu-devel@nongnu.org; Thu, 18 Jun 2009 15:48:30 -0400 Received: from [199.232.76.173] (port=38667 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MHNb0-0003l3-A7 for qemu-devel@nongnu.org; Thu, 18 Jun 2009 15:48:26 -0400 Received: from cheetah.cs.fiu.edu ([131.94.130.107]:35027) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MHNaz-0005BC-Ob for qemu-devel@nongnu.org; Thu, 18 Jun 2009 15:48:25 -0400 Date: Thu, 18 Jun 2009 15:48:20 -0400 From: Luis Useche Subject: Re: [Qemu-devel] Memory Traces for System Simulation Message-ID: <20090618194820.GA19814@meg.cs.fiu.edu> References: <20090617215018.GA32029@meg.local> <20090618152005.GC16663@edde.se.axis.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090618152005.GC16663@edde.se.axis.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Edgar E. Iglesias" Cc: qemu-devel@nongnu.org On Thu, Jun 18, 2009 at 05:20:05PM +0200, Edgar E. Iglesias wrote: > On Wed, Jun 17, 2009 at 05:50:18PM -0400, Luis Useche wrote: > > Hi Guys, > > Hello Luis, Thanks for the response. > > At the moment, I am instrumenting several functions in exec.c as my trace > > points: > > ldl_phys > > ldq_phys > > ldup_phys > > lduw_phys > > stl_phys_notdirty > > stq_phys_notdirty > > stl_phys > > stb_phys > > stw_phys > > stq_phys > > Depending on what you want to do and on your cache arch you might need > to log both virtual and physical addresses. I don't know what the best > place to hook in would be though. If I can find the physical addresses that would be really great. And if I can find both physical and virtual it would be even better. In any case, I need to know what section of the code is the most likely to have this memory operations to trace them. > > I would really appreciate any suggestion you have in order to solve my > > problem. If you have any insights in the solutions I explained above I > > would be very thankful. > > > > Given that many people seems to be having the same problem than I, it > > would be nice to have an actual framework that add this functionality to > > qemu. I can offer myself to do that as long as I have enough help. > > > > As a parallel question: Does qemu simulate CPU cache? i.e. There is always > > Nope. > > > memory access even when this would not happen in a real system due to CPU > > cache? > > Yes correct. > > I've got a pretty nasty hack that online emulates controller and tag > memories. I find it useful for profiling and for some debugging. The data > memories are not emulated so accesses are never absorbed. I don't think > it's very useful for scientific purposes.. > > Anyway, it kind of works for CRIS and MicroBlaze. Feel free to look around > on the cris git at your own risk :) > git://repo.or.cz/qemu/cris-port.git This can probably helps. Can you give me more information of what this does. Best, -- Luis Useche Ph.D. Student Florida International University