qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Shashidhar Mysore" <shashimc@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] address translation
Date: Fri, 13 Jul 2007 15:17:01 -0700	[thread overview]
Message-ID: <12835c8f0707131517t72febf40h27326ab67d5b32f3@mail.gmail.com> (raw)
In-Reply-To: <fb249edb0707131259i1c2b0ebbi1af8355d85d191ea@mail.gmail.com>

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

Thanks for the reply, Andrzej!

Some clarifications below ...

On 7/13/07, andrzej zaborowski <balrogg@gmail.com> wrote:

> >
> > ************************************************
> > /* convert one instruction. s->is_jmp is set if the translation must
> >    be stopped. Return the next pc value */
> > static target_ulong disas_insn(DisasContext *s, target_ulong pc_start)
> > {
> >     int b, prefixes, aflag, dflag;
> >     int shift, ot;
> >     int modrm, reg, rm, mod, reg_addr, op, opreg, offset_addr, val;
> >     target_ulong next_eip, tval;
> >     int rex_w, rex_r;
> >
> >     s->pc = pc_start;   // This s->pc is what I am using to extract all
> > executed PC values
>
> This s->pc doesn't correspond to executed PC values, qemu is a translator.


Can you tell me what s->pc is, in this context? Is the the start PC of a
basic block that is about to be executed? Is there any way in which I could
extract the trace of executed PCs in QEMU?


Regards,
-Shashi.

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

  reply	other threads:[~2007-07-13 22:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-13  0:29 [Qemu-devel] address translation Shashidhar Mysore
2007-07-13 19:59 ` andrzej zaborowski
2007-07-13 22:17   ` Shashidhar Mysore [this message]
2007-07-13 22:23     ` andrzej zaborowski
2007-07-17 20:43       ` Shashidhar Mysore

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=12835c8f0707131517t72febf40h27326ab67d5b32f3@mail.gmail.com \
    --to=shashimc@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).