From: "aditya bhandari" <adi.bhandari@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Softmmu modification: Memory access functions
Date: Sat, 22 Sep 2007 09:36:40 -0500 [thread overview]
Message-ID: <c63970600709220736n3856f189q76d86073ec2d7285@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 850 bytes --]
Hi,
I've been trying to figure out how to modify the softmmu for x86. I am only
interested in system emulation at the moment. I've being trying to figure
out the memory access functions, but the number of macros used makes this
somewhat complicated. I have a few questions:
1. What is the difference between functions with suffix _mmu and those with
suffix _cmmu?
2. What do the 4 values of the ACCESS_TYPE macro designate?
3. What is the difference between _raw, _kernel, and _user? Which ones are
applicable to system emulation?
I also want to be able to intercept every physical memory access (I want to
do some cache statistics experiments). Is there a single function (or maybe
one for read and one for write) that all these accesses go through? I see
several such as ldul_le_p (for example), cpu_physical_memory_rw, ldq_phys.
Thanks.
Aditya
[-- Attachment #2: Type: text/html, Size: 895 bytes --]
reply other threads:[~2007-09-22 14:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=c63970600709220736n3856f189q76d86073ec2d7285@mail.gmail.com \
--to=adi.bhandari@gmail.com \
--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).