From: "Alex Bennée" <alex.bennee@linaro.org>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: Ayaz Akram <aaqemu@gmail.com>,
Peter Crosthwaite <peter.crosthwaite@xilinx.com>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@gmail.com>
Subject: Re: [Qemu-devel] QEMU to generate host binary
Date: Tue, 30 Jun 2015 13:21:16 +0100 [thread overview]
Message-ID: <877fql75fn.fsf@linaro.org> (raw)
In-Reply-To: <20150630112608.GC2142@work-vm>
Dr. David Alan Gilbert <dgilbert@redhat.com> writes:
> * Ayaz Akram (aaqemu@gmail.com) wrote:
>> Thanks for your answers. The thing that i still do not get is once we have
>> host assembly code (output assembly log generated for compiled TBs ),
>> should we still worry about problems like self modifying code and other
>> dynamic conditions? Moreover, assuming static linking, will not this code
>> be enough to generate .text section of an executable that could be run
>> directly on host (if somehow other sections of that host executable can be
>> generated, which is itself difficult) ?
>
> It can certainly help, but you can still walk into a piece of code
> that you've not previously translated, and a shared library for example
> might change, and your code might change due to other things such as
> randomisation of library loading addresses.
<snip>
> You say 'should we still worry about problems like self modifying code and other
> dynamic conditions?' - well you hope that for most 'normal' programs that
> self modification doesn't happen; but it keeps turning up even when you don't
> expect it, e.g. loading/unloading of plugins or if you happen to be
> emulating a JIT (such as qemu!).
I think PLT patching is another case of self modifying code you often
come across.
--
Alex Bennée
prev parent reply other threads:[~2015-06-30 12:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 19:33 [Qemu-devel] QEMU to generate host binary Ayaz Akram
2015-06-27 3:34 ` Peter Crosthwaite
[not found] ` <CAC0+NVaM-8W+WvDa+dHJVbomR3odwbMOCxZ98KHE=EV-8jpuXw@mail.gmail.com>
2015-06-28 23:29 ` Ayaz Akram
2015-06-29 15:13 ` Stefan Hajnoczi
2015-06-29 17:04 ` Peter Crosthwaite
2015-06-29 21:14 ` Ayaz Akram
2015-06-30 11:26 ` Dr. David Alan Gilbert
2015-06-30 12:21 ` Alex Bennée [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=877fql75fn.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=aaqemu@gmail.com \
--cc=dgilbert@redhat.com \
--cc=peter.crosthwaite@xilinx.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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).