From: "coopht@gmail.com" <coopht@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Question about memory micro operations in Qemu 0.12.x
Date: Fri, 26 Mar 2010 23:23:30 +0300 [thread overview]
Message-ID: <4BAD17C2.2090801@gmail.com> (raw)
Hello.
in qemu 0.9.x there was a special file with micro-operations, which
implemented access to memory. For example for arm architecture it was
op_mem.h file. I was able to add some printfs to this functions and get
information about memory accesses.
My question is : how memory access microoperations are now implemented
in qemu 0.12.x ?
Thanks for you answers.
next reply other threads:[~2010-03-26 20:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-26 20:23 coopht [this message]
[not found] ` <20100327094900.GA4172@zubnet.me.uk>
2010-03-29 7:30 ` [Qemu-devel] Question about memory micro operations in Qemu 0.12.x Alexander
-- strict thread matches above, loose matches on Subject: below --
2010-03-19 10:31 [Qemu-devel] [PATCH] remove remaining occurrences AREG[1-9] and TCG_AREG[1-9] Paolo Bonzini
2010-03-26 22:22 ` Aurelien Jarno
2010-03-27 6:20 ` [Qemu-devel] Question about memory micro operations in Qemu 0.12.x coopht
2010-03-27 9:52 ` Stuart Brady
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=4BAD17C2.2090801@gmail.com \
--to=coopht@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).