Re: [Qemu-devel] Storing code caching

[Julian Seward]

> 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