All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Byron Hawkins" <byronh@uci.edu>
To: QEMU Developer List <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Running programs that dynamically generate code
Date: Thu, 28 Aug 2014 19:24:32 -0700	[thread overview]
Message-ID: <36d601cfc330$5eb23ea0$1c16bbe0$@uci.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 850 bytes --]

Hi, I'm working on a research project to optimize binary translation for
target applications that dynamically generate code, such as browser JIT
engines. When I run the octane benchmark in Chrome v8 under QEMU (i.e.,
qemu-x86_64), it shows significant overhead compared to a native run. Can
someone tell me how QEMU maintains consistency with the target application
when it dynamically generates code? For example, does it set executable
pages readonly and catch the page fault when the target app writes to it? I
searched the documentation and mailing list, but all the references to
"dynamically generated code" and "JIT" are about code generated by QEMU, not
about code generated by the target application. If there is a document about
this somewhere, please send me a link-or just a basic explanation would also
be very helpful. Thanks.


Byron


[-- Attachment #2: Type: text/html, Size: 2653 bytes --]

             reply	other threads:[~2014-08-29  2:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-29  2:24 Byron Hawkins [this message]
2014-08-29  9:22 ` [Qemu-devel] Running programs that dynamically generate code Peter Maydell
2014-09-02  8:16   ` Byron Hawkins
2014-09-02  8:50     ` Peter Maydell

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='36d601cfc330$5eb23ea0$1c16bbe0$@uci.edu' \
    --to=byronh@uci.edu \
    --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.