From: Steven <wangwangkang@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org, "陳韋任 (Wei-Ren Chen)" <chenwj@iis.sinica.edu.tw>
Subject: Re: [Qemu-devel] qemu log function to print out the registers of the guest
Date: Thu, 16 Aug 2012 15:31:02 -0400 [thread overview]
Message-ID: <CAMTrTqVN7SSa_qrY3rM2b9PUStf9aoDf75wTMs=-_76tkO=5oA@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA9UQk_BuGgLMZEEzfaQFj=XZ_B_cLsn1SMtqD=1Bs76_Q@mail.gmail.com>
On Thu, Aug 16, 2012 at 12:54 PM, Peter Maydell
<peter.maydell@linaro.org> wrote:
> On 16 August 2012 17:36, Steven <wangwangkang@gmail.com> wrote:
>> I would like to get a trace of guest memory access. So I can not use
>> "info registers".
>> What I want to do is that when tcg fetches a load instruction at
>> disas_insns(), the guest memory address should be calculated.
>
> You cannot calculate the guest memory address at the point where
> TCG is translating the load instruction. This is because that
> address depends on the values of guest registers at runtime.
> At translation time these values are not known. Also they may
> be different for different runs through the same generated code.
>
> QEMU is a just-in-time translator (JIT). For a JIT it is
> important to remember the difference between:
> * translation time. Here we know what the guest code (instructions)
> are, but we do not know what the guest CPU registers will be
> * run time. This may be some time later, and we may execute
> the same code several times. We don't have any access to
> information about the guest code we are running unless
> we specifically recorded it at translation time.
To verify what is translation time and what is the run time, I log the
register information before disassembling each guest code. I copied
some results from the log file, which is generated at run time of a
guest machine.
EAX=00000000 EBX=00006ffc
IN:
0x00000000000f2087: mov $0xf5588,%eax
EAX=000f5588 EBX=00006ffc
IN:
0x00000000000f208B: move 0x4(%ebx) %eax
The first instruction load eax with the value 0xf5588, so the eax at
the second instruction is EAX=000f5588. So can I consider the memory
address of 0x4(%ebx) as (00006ffc + 4)? I think this should be the
run time information I need. Please correct me if there is anything
wrong. Thanks.
>
> When you are reading (or trying to change) QEMU source code
> you need to know whether the QEMU code will be running at
> translation or run time. The answer affects what information
> you have access to, and what you can do to the guest.
>
> -- PMM
next prev parent reply other threads:[~2012-08-16 19:31 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 7:21 [Qemu-devel] qemu log function to print out the registers of the guest Steven
2012-08-16 8:02 ` 陳韋任 (Wei-Ren Chen)
2012-08-16 16:36 ` Steven
2012-08-16 16:54 ` Peter Maydell
2012-08-16 17:13 ` Steven
2012-08-16 17:15 ` Peter Maydell
2012-08-16 17:26 ` Steven
2012-08-16 19:31 ` Steven [this message]
2012-08-17 10:26 ` 陳韋任 (Wei-Ren Chen)
2012-08-16 17:00 ` Max Filippov
2012-08-16 17:29 ` Steven
2012-08-16 17:37 ` Max Filippov
2012-08-16 17:43 ` Max Filippov
2012-08-16 17:49 ` Steven
2012-08-16 18:31 ` Max Filippov
2012-08-16 21:18 ` Max Filippov
2012-08-17 5:38 ` Steven
2012-08-17 6:38 ` Max Filippov
2012-08-16 18:51 ` Laurent Desnogues
2012-08-16 19:02 ` Steven
2012-08-17 11:14 ` 陳韋任 (Wei-Ren Chen)
2012-08-17 11:57 ` Max Filippov
2012-08-19 8:33 ` 陳韋任 (Wei-Ren Chen)
2012-08-21 5:40 ` Steven
2012-08-21 7:18 ` Max Filippov
[not found] ` <CAMTrTqVF0EGEqC8qZHOV5RHYxq=MHYuu_X0V5va5gkyaRQWJuw@mail.gmail.com>
2012-08-25 20:41 ` Max Filippov
2012-08-27 16:15 ` Steven
2012-08-28 3:14 ` 陳韋任 (Wei-Ren Chen)
2012-08-28 3:44 ` Steven
2012-08-28 10:48 ` Max Filippov
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='CAMTrTqVN7SSa_qrY3rM2b9PUStf9aoDf75wTMs=-_76tkO=5oA@mail.gmail.com' \
--to=wangwangkang@gmail.com \
--cc=chenwj@iis.sinica.edu.tw \
--cc=peter.maydell@linaro.org \
--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).