qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: S.P.T.Krishnan <sptkrishnan@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu dynamic translation (system design) question
Date: Sun, 20 Aug 2006 23:23:11 +0800	[thread overview]
Message-ID: <3ed52ec0608200823y6e803330q8ece342dde16945e@mail.gmail.com> (raw)
In-Reply-To: <5226555.1155980264507.JavaMail.www@wwinf1629>

Hi Laurent,

Thanks for the direction.

I am just thinking.  If I run a guest OS once and observe the blocks
that are translated and may be reused.  Then I again re-run the OS,
can I expect the same blocks are translated ?  i.e., is qemu
consistent on how it partitions the asm into blocks on successive runs
or the guest OS ?

Note: in both cases the user doesn't interact with the Guest OS.  It
is up for, say 1 min and then shutdown in both runs.

regards,
Krishnan

On 8/19/06, Laurent DESNOGUES <laurent.desnogues@wanadoo.fr> wrote:
> > b. Once a block is generated some ID should be assigned to it right ?
> > in which src file it is stored ?
> > c. The next time a src block with the same signature is encountered
> > the cached host binary is used right ?  -- How does qemu detect that
> > is the same guest block ? md5sum or other fingerprinting methods ?
>
> Look in qemu-exec.c/tb_find_fast
>
>
> Laurent
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>

  reply	other threads:[~2006-08-20 15:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-19  9:37 [Qemu-devel] qemu dynamic translation (system design) question Laurent DESNOGUES
2006-08-20 15:23 ` S.P.T.Krishnan [this message]
2006-08-20 23:48   ` Re[2]: " Paul Sokolovsky
  -- strict thread matches above, loose matches on Subject: below --
2006-08-19  9:00 S.P.T.Krishnan
2006-08-24 17:52 ` ByteRage

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=3ed52ec0608200823y6e803330q8ece342dde16945e@mail.gmail.com \
    --to=sptkrishnan@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).