From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Profiling Qemu for speed?
Date: Sun, 17 Apr 2005 11:27:35 +0100 [thread overview]
Message-ID: <200504171127.36489.paul@codesourcery.com> (raw)
In-Reply-To: <70867645caaf37338ce6a98cdfb0bdc2@elis.ugent.be>
On Sunday 17 April 2005 09:59, Jonas Maebe wrote:
> On 17 Apr 2005, at 10:21, John R. Hogerhuis wrote:
> > One thought would be to have a peephole optimizer that looks back over
> > the just translated basic block (or a state machine that matches such
> > sequences as an on-line algorithm) and match against common, known
> > primitive sequences, and replaces them with optimized versions.
>
> Another thing I've thought about is checking what sequences of
> instructions often appear in x86 programs (such as e.g. "push %ebp;
> movl %esp, %ebp") and then creating C-functions which emulate such an
> antire block, so they can be optimized as a whole by gcc. That would
> give a similar performance gain on all supported targets, and not just
> on the one you created the peephole optimizer for (+ less work to
> debug).
Unfortunately it's not that simple. The push instruction may cause an
exception. Whatever optimizations you apply you've got to make sure that the
guest state is still consistent when the exception occurs.
Paul
next prev parent reply other threads:[~2005-04-17 10:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-17 5:58 [Qemu-devel] Profiling Qemu for speed? Joe Luser
2005-04-17 8:21 ` John R. Hogerhuis
2005-04-17 8:59 ` Jonas Maebe
2005-04-17 10:27 ` Paul Brook [this message]
2005-04-17 10:46 ` Jonas Maebe
2005-04-18 1:36 ` Nathaniel G H
2005-04-18 2:11 ` John R. Hogerhuis
2005-04-18 2:39 ` André Braga
2005-04-18 4:31 ` Karl Magdsick
2005-04-17 10:36 ` Paul Brook
-- strict thread matches above, loose matches on Subject: below --
2005-04-18 8:35 Daniel J Guinan
2005-04-18 9:51 ` Ian Rogers
2005-04-18 13:44 ` Daniel Egger
2005-04-18 14:12 ` Christian MICHON
2005-04-18 14:29 ` Ian Rogers
2005-04-18 14:19 ` Ian Rogers
2005-04-18 14:40 ` Paul Brook
2005-04-18 11:24 Daniel J Guinan
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=200504171127.36489.paul@codesourcery.com \
--to=paul@codesourcery.com \
--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).