qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "João Corrêa" <joao.lvwr@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Doubts about qemu tcg/tci
Date: Thu, 1 Mar 2012 17:45:01 -0300	[thread overview]
Message-ID: <CALMZKf7o1uhpcTYLoODUu9P7M+zSaxeQsPA7XMnZ7q24KyRSWQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1338 bytes --]

Hi,

Hopefully I'm sending this e-mail to the right list. If not, please ignore
it!

I'm trying to read the asm code generated with the -D qemu option, but I am
having some difficulties.

First, I've seen that the generated asm is allocated in different address
ranges. The beginning of the dump says:

end_code    0x080486dc
start_code  0x08048000

but the first instruction's address is: 0x6022caf0

Am I misunderstanding something? How exactly this reallocation happens (or
where in the source code am I able to track and understand the process)?

Second, what exactly means the identifying letters of arguments counted in
front of each instruction (i, o, c) ? Is it too hard to create a patch on
the disassembly function to also output its values?

Third, Is there a trivial way for me to track an original function inside
the generated asm dump? I mean, if I create a C function called foo(), that
is called somewhere inside the main function, what should I do in order to
find the translated instructions inside the outputted dump?

Finally, I've been trying to find material about how this translation works
properly, but I've been unable to find much. Is there something I should be
reading before asking around here? If yes, please, point me to it!

Thank you for your time. Any help with any question will be very useful to
me.

[-- Attachment #2: Type: text/html, Size: 1790 bytes --]

             reply	other threads:[~2012-03-01 20:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-01 20:45 João Corrêa [this message]
2012-03-02  3:30 ` [Qemu-devel] Doubts about qemu tcg/tci 陳韋任
     [not found]   ` <CALMZKf5LHXaOoZa=nSuxX1_4YY2vBCQHKbLU9aoafG17huU16A@mail.gmail.com>
2012-03-14  3:04     ` 陳韋任

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=CALMZKf7o1uhpcTYLoODUu9P7M+zSaxeQsPA7XMnZ7q24KyRSWQ@mail.gmail.com \
    --to=joao.lvwr@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).