From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GvqJS-0002U1-4t for qemu-devel@nongnu.org; Sun, 17 Dec 2006 02:19:58 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GvqJQ-0002R7-Ez for qemu-devel@nongnu.org; Sun, 17 Dec 2006 02:19:57 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GvqJQ-0002Qh-29 for qemu-devel@nongnu.org; Sun, 17 Dec 2006 02:19:56 -0500 Received: from [66.249.92.174] (helo=ug-out-1314.google.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1GvqJP-0001FK-T3 for qemu-devel@nongnu.org; Sun, 17 Dec 2006 02:19:56 -0500 Received: by ug-out-1314.google.com with SMTP id j40so1169938ugd for ; Sat, 16 Dec 2006 23:19:54 -0800 (PST) Message-ID: <891be9410612162319o7828c31ehc3bcf986a3ea991e@mail.gmail.com> Date: Sat, 16 Dec 2006 23:19:54 -0800 From: "Diwaker Gupta" Subject: Re: [Qemu-devel] Tracing guest memory accesses In-Reply-To: <20061217035307.GA32712@nevyn.them.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <891be9410612161942t28116f7w12123ebca0ca6278@mail.gmail.com> <20061217035307.GA32712@nevyn.them.org> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On 12/16/06, Daniel Jacobowitz wrote: > On Sat, Dec 16, 2006 at 07:42:46PM -0800, Diwaker Gupta wrote: > > o do these changes seem correct? As in, do they actually track the > > read/write memory accesses done by the guest? I was concerned because > > when I start a guest, I see a whole lot of writes and not as many > > reads, which seems a little counter intuitive. > > No. Those are I/O device accesses, not memory accesses. Look at the > softmmu code instead. Like I said, I did add some debugging code to softmmu_template.h. The read/writes I'm seeing are being generated by that softmmu debugging code, not the iommu code. Sorry if I wasn't clear. Is there some other softmmu code I should be looking at? > It may be easiest to add some new instrumentation in the translation > code for whatever target you're interested in. I'm just focusing on Linux i386. I'm only beginning to explore the qemu source, so any pointer to files/functions I should look at will be much appreciated! TIA, Diwaker -- Web/Blog/Gallery: http://floatingsun.net/blog