From: Julian Seward <jseward@acm.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Storing code caching
Date: Thu, 8 Jul 2004 20:11:54 +0100 [thread overview]
Message-ID: <200407082011.54991.jseward@acm.org> (raw)
In-Reply-To: <431F9EDC-D108-11D8-8B8C-000A95B1EB4C@mac.com>
> The program I would write would basically use the qemu core to process
> an entire executable, creating the blocks that are executable on the
> host machine, and store them. Then start work on modifying qemu to
> recognise the existense of the cache file and use the blocks. Then deal
> with the self-modyfing code issue as above ...
Nice idea, but ... I suspect it solves a non-problem really. Caching
translations is only worthwhile when translation time is a large
part of overall run time, but I bet that's not the case. It certainly
isn't with Valgrind, which uses similar technology.
If you want to throw lots of hacking effort at QEMU to make it
go faster, I suspect you'll need to be building a more sophisticated
code generator, a la "lcc" (http://www.cs.princeton.edu/software/lcc).
That's a lot of work, though.
J
next prev parent reply other threads:[~2004-07-08 19:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-08 12:26 [Qemu-devel] Storing code caching Martin Williams
2004-07-08 17:05 ` John R. Hogerhuis
2004-07-08 17:25 ` Antony T Curtis
2004-07-08 18:42 ` [spam score 1/10 -pobox] " John R. Hogerhuis
2004-07-08 19:42 ` Re[2]: " Igor Shmukler
2004-07-08 17:57 ` Martin Williams
2004-07-08 18:28 ` John R. Hogerhuis
2004-07-08 19:11 ` Julian Seward [this message]
2004-07-08 19:45 ` John R. Hogerhuis
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=200407082011.54991.jseward@acm.org \
--to=jseward@acm.org \
--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).