From: Avi Kivity <avi@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: "felix.matenaar@rwth-aachen" <felix.matenaar@rwth-aachen.de>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Cooperative BBL execution due to binary translation
Date: Sun, 16 Oct 2011 16:30:13 +0200 [thread overview]
Message-ID: <4E9AEA75.3090801@redhat.com> (raw)
In-Reply-To: <CAAu8pHvtSHnfS76mPCfYzeoTMnybgzK7kyGEWa3vLZcq9F6Z2A@mail.gmail.com>
On 10/16/2011 02:06 PM, Blue Swirl wrote:
> >
> > c = get_executable_memory(1Gb)
> > set(c, OPCODE_NOP, sizeof c)
> > jmp_into c
>
> Not really, we don't care very much about such timing problems.
> Translation is limited so that the intermediate buffer does not
> overflow, also page boundaries may not be crossed. If an instruction
> may cause a fault, it will terminate the block.
On x86 an instruction may cross page boundary. So an instruction that
begins in one page may be interpreted differently depending on the
contents of the second page. But I see that the code handles it cleverly.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2011-10-16 14:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-16 2:19 [Qemu-devel] Cooperative BBL execution due to binary translation felix.matenaar@rwth-aachen
2011-10-16 12:06 ` Blue Swirl
2011-10-16 14:30 ` Avi Kivity [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=4E9AEA75.3090801@redhat.com \
--to=avi@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=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).