From: "Màrius Montón" <marius.monton@uab.cat>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] tracing memory accesses
Date: Tue, 11 Nov 2008 11:01:45 +0100 [thread overview]
Message-ID: <49195809.6010702@uab.cat> (raw)
[-- Attachment #1: Type: text/plain, Size: 1169 bytes --]
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/freeabs_all.jsp?arnumber=4374971)
Now it's time to move a whole system to a SystemC described one but the CPU. My plan is to use QEMU CPU emulation and substitute all peripherals by its SystemC description and communicate using any sort of bus in SystemC too.
So I need to capture all memory accesses from CPU to Memory. I've been 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 manage stores from CPU to memory. I can see some equivalent functions called 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 functions is enough to capture all data moving from CPU to RAM?
Thank you!
Màrius
P.S.: I noticed that Argos did similar work, but since they are focused on a very different target, this work should be started from scratch.
[-- Attachment #2: marius_monton.vcf --]
[-- Type: text/x-vcard, Size: 369 bytes --]
begin:vcard
fn;quoted-printable:M=C3=A0rius Monton
n;quoted-printable:Monton;M=C3=A0rius
org:CEPHIS-UAB
adr;quoted-printable:Bellaterra;;QC-2090D, ETSE. Campus de la UAB;Cerdanyola del Vall=C3=A8s;;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
next reply other threads:[~2008-11-11 10:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-11 10:01 Màrius Montón [this message]
2008-11-11 11:10 ` [Qemu-devel] tracing memory accesses Erik de Castro Lopo
2008-11-11 11:21 ` Laurent Desnogues
2008-11-11 11:26 ` Màrius Montón
2008-11-11 18:51 ` Blue Swirl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49195809.6010702@uab.cat \
--to=marius.monton@uab.cat \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).