From: "felix.matenaar@rwth-aachen" <felix.matenaar@rwth-aachen.de>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Cooperative BBL execution due to binary translation
Date: Sun, 16 Oct 2011 04:19:14 +0200 [thread overview]
Message-ID: <4E9A3F22.6030105@rwth-aachen.de> (raw)
Hi *,
I have the following question regarding qemu binary translation of
target-i386 (and maybe other targets):
As far as I understood the code, when a basic block is executed, there
is no event which can interrupt the execution until the bbl reaches its
end and the control flow is then back at qemu. Is this right? Stumbled
over this when asking me why basic blocks are sometimes divided even if
there is no branch in it.
If so, is the reason for this that some application like that could
cause timing problems:
c = get_executable_memory(1Gb)
set(c, OPCODE_NOP, sizeof c)
jmp_into c
Regards,
Felix
next reply other threads:[~2011-10-16 2:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-16 2:19 felix.matenaar@rwth-aachen [this message]
2011-10-16 12:06 ` [Qemu-devel] Cooperative BBL execution due to binary translation Blue Swirl
2011-10-16 14:30 ` Avi Kivity
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=4E9A3F22.6030105@rwth-aachen.de \
--to=felix.matenaar@rwth-aachen.de \
--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).