All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lluís <xscript@gmx.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Binary translation (of code)
Date: Sun, 08 May 2011 21:41:15 +0200	[thread overview]
Message-ID: <87ei49ugis.fsf@ginnungagap.bsc.es> (raw)
In-Reply-To: <227989.48678.qm@web38406.mail.mud.yahoo.com> (Tarmo Pikaro's message of "Sun, 8 May 2011 12:02:02 -0700 (PDT)")

Tarmo Pikaro writes:

> Hi !
>> > I think self-modifying code is kinda rare case - it's made typically for
>> > protection againt hackers , and typically on pc side. Nintendo roms probably
>> > don't use this kind of
>> > protection.
>> 
>> It doesn't have to be protection, for example GCC generates
>> trampolines to stack when using nested functions.

> Ok, so apparently we will have some challenges on the way.

> I guess some sort of mutation - qemu + recompiler could be done as well...

It would be much easier to ship an executable containing both the guest
application and qemu, so that executing it starts qemu with a
pre-defined configuration and runs the guest binary.


Lluis

-- 
 "And it's much the same thing with knowledge, for whenever you learn
 something new, the whole world becomes that much richer."
 -- The Princess of Pure Reason, as told by Norton Juster in The Phantom
 Tollbooth

  reply	other threads:[~2011-05-08 19:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-07 11:26 [Qemu-devel] Binary translation (of code) Tarmo Pikaro
2011-05-08  8:40 ` Mulyadi Santosa
2011-05-08 10:22 ` Blue Swirl
2011-05-08 13:05   ` Tarmo Pikaro
2011-05-08 13:46     ` Blue Swirl
2011-05-08 13:54       ` Stefan Hajnoczi
2011-05-08 19:02       ` Tarmo Pikaro
2011-05-08 19:41         ` Lluís [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-05-10 18:13 Tarmo Pikaro
2011-05-10 19:46 ` Richard Henderson
2011-05-10 20:02 ` Lluís

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=87ei49ugis.fsf@ginnungagap.bsc.es \
    --to=xscript@gmx.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.