From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Kzq5t-0008Si-Rt for qemu-devel@nongnu.org; Tue, 11 Nov 2008 05:03:33 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Kzq5s-0008SD-8A for qemu-devel@nongnu.org; Tue, 11 Nov 2008 05:03:33 -0500 Received: from [199.232.76.173] (port=36855 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Kzq5r-0008S9-Ug for qemu-devel@nongnu.org; Tue, 11 Nov 2008 05:03:32 -0500 Received: from damascus.uab.es ([158.109.168.135]:50185) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Kzq5r-0005K1-6d for qemu-devel@nongnu.org; Tue, 11 Nov 2008 05:03:31 -0500 Received: from damascus.uab.es ([127.0.0.1]) by damascus.uab.es (Sun Java System Messaging Server 6.1 HotFix 0.10 (built Jan 6 2005)) with ESMTP id <0KA50096OYIJ4N10@damascus.uab.es> for qemu-devel@nongnu.org; Tue, 11 Nov 2008 11:01:31 +0100 (CET) Received: from [192.168.1.2] ([87.217.235.67]) by damascus.uab.es (Sun Java System Messaging Server 6.1 HotFix 0.10 (built Jan 6 2005)) with ESMTPA id <0KA500G1GYIIPL80@damascus.uab.es> for qemu-devel@nongnu.org; Tue, 11 Nov 2008 11:01:31 +0100 (CET) Date: Tue, 11 Nov 2008 11:01:45 +0100 From: =?ISO-8859-1?Q?M=E0rius_Mont=F3n?= Message-id: <49195809.6010702@uab.cat> MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_w/UGBwX63ojcMTKZN2ZzyA)" Subject: [Qemu-devel] tracing memory accesses 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 This is a multi-part message in MIME format. --Boundary_(ID_w/UGBwX63ojcMTKZN2ZzyA) Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: QUOTED-PRINTABLE Hello, I've been working for a while adding SystemC capabilities to QEMU (in= short, SystemC is a C++ extension to describe HW and we are using it= to add new peripherals to QEMU) (http://ieeexplore.ieee.org/xpl/free= abs_all.jsp?arnumber=3D4374971) Now it's time to move a whole system to a SystemC described one but t= he CPU. My plan is to use QEMU CPU emulation and substitute all perip= herals by its SystemC description and communicate using any sort of b= us in SystemC too. So I need to capture all memory accesses from CPU to Memory. I've bee= n looking at code, and I can see that ldq_phys, ldl_phys (in exec.c) = are used to load from memory to CPU, but I'm not able to see what functions are used to man= age stores from CPU to memory. I can see some equivalent functions ca= lled stl_phys_notdirty and stl_phys, but they never used (I'm focused= in ARM platforms). Do you have any hint about that? Do you think managing these function= s is enough to capture all data moving from CPU to RAM? Thank you! M=E0rius P.S.: I noticed that Argos did similar work, but since they are focus= ed on a very different target, this work should be started from scrat= ch. --Boundary_(ID_w/UGBwX63ojcMTKZN2ZzyA) Content-type: text/x-vcard; charset=utf-8; name=marius_monton.vcf Content-transfer-encoding: QUOTED-PRINTABLE Content-disposition: attachment; filename=marius_monton.vcf begin:vcard fn;quoted-printable:M=3DC3=3DA0rius Monton n;quoted-printable:Monton;M=3DC3=3DA0rius org:CEPHIS-UAB adr;quoted-printable:Bellaterra;;QC-2090D, ETSE. Campus de la UAB;Cer= danyola del Vall=3DC3=3DA8s;;08015;Spain email;internet:marius.monton@uab.cat title:R&D Engineer tel;work:+34 93 581 35 34 x-mozilla-html:TRUE url:cephis.uab.cat version:2.1 end:vcard --Boundary_(ID_w/UGBwX63ojcMTKZN2ZzyA)--