From: Paul Sokolovsky <pmiscml@gmail.com>
To: "S.P.T.Krishnan" <sptkrishnan@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re[2]: [Qemu-devel] qemu dynamic translation (system design) question
Date: Mon, 21 Aug 2006 02:48:20 +0300 [thread overview]
Message-ID: <576442285.20060821024820@gmail.com> (raw)
In-Reply-To: <3ed52ec0608200823y6e803330q8ece342dde16945e@mail.gmail.com>
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 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.
My 2 cents of pure scholastic reasoning:
Let's assume that QEMU uses deterministic rules for block
translation. Then, it just translates what CPU goes thru. Does any
contemporary OS leads CPU in deterministic ways? No. It largely
depends on various environment parameters, of which user interaction
is not the last. There're interrupts occuring in rather random places
with respect to mainline execution, I/O delays, etc. As these
parameters in guest OS depend on QEMU's interaction with host OS, they
are not deterministic in it either. Well, but does QEMU's translation
itself deterministic? Not really, as it uses caches, and thus depend on
memory parameters in host OS.
> regards,
> Krishnan
--
Best regards,
Paul mailto:pmiscml@gmail.com
prev parent reply other threads:[~2006-08-20 23:48 UTC|newest]
Thread overview: 3+ 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
2006-08-20 23:48 ` Paul Sokolovsky [this message]
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=576442285.20060821024820@gmail.com \
--to=pmiscml@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=sptkrishnan@gmail.com \
/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).