From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1HDmL0-0003IU-L2
	for qemu-devel@nongnu.org; Sun, 04 Feb 2007 13:43:42 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1HDmKx-0003Hq-GJ
	for qemu-devel@nongnu.org; Sun, 04 Feb 2007 13:43:42 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1HDmKx-0003Hn-D2
	for qemu-devel@nongnu.org; Sun, 04 Feb 2007 13:43:39 -0500
Received: from warsl404pip8.highway.telekom.at ([195.3.96.102]
	helo=email.aon.at) by monty-python.gnu.org with esmtp (Exim 4.52)
	id 1HDmKw-0003GK-PT
	for qemu-devel@nongnu.org; Sun, 04 Feb 2007 13:43:39 -0500
Received: from m731p027.adsl.highway.telekom.at (HELO [192.168.1.4])
	([62.47.251.91]) (envelope-sender <maestro82@gmail.com>)
	by smarthub75.highway.telekom.at (qmail-ldap-1.03) with SMTP
	for <qemu-devel@nongnu.org>; 4 Feb 2007 18:43:36 -0000
Subject: Re: [Qemu-devel] Tracing memory accesses by emulated systems
From: maestro <maestro82@gmail.com>
In-Reply-To: <20070204161752.GA7610@core>
References: <20070204161752.GA7610@core>
Content-Type: text/plain
Date: Sun, 04 Feb 2007 19:43:34 +0100
Message-Id: <1170614615.2110.3.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
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

Am Sonntag, den 04.02.2007, 17:17 +0100 schrieb Christian Leber:
> Hello,
> 
> I would like to trace all "physical" memory read/write operations for x86_64,
> but I have to admit that I'm not sure where exactly this has to be
> implemented.
> 
> Could somebody give me some hints where and how I could do that?
> (or is there already a patch that does this? on irc somebody suggested
> that something like that could exist, but I was not able to find it)
> 
> Regards
> 
> Christian Leber
hello christian!

i'm not sure if it applies for 64bit (but i'd assume it does).
afaik the easiest way to catch "all" (dma operations are not covered
there - i think) memory accesses is via the ld*,st* macros in
softmmu_helper.h and softmmu_header.h. at least this is the way i did
that.

cheers
m.