--- "S.P.T.Krishnan" <[EMAIL PROTECTED]> wrote:
> a. How does qemu slice the guest binary into blocks
> ? any rational or rule of thumb here ?
As far as I understand the source code, the end of
every translated block is at a control transfer
instruction or when a maximum translation block length
Hello S.P.T.Krishnan,
Sunday, August 20, 2006, 6:23:11 PM, you wrote:
> 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 transla
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 succe
> 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 fingerp
Hi,
I would like to understand certain aspects of dynamic translation
which Qemu employs to run the guest OS. I have read the qemu paper
and this query is beyond that.
My understanding is as follows:
1. Qemu slices the guest os binary into blocks and then asks the Host
OS to execute it and retu
