From: Fabrice Bellard <fabrice.bellard@free.fr>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Basic block statistics
Date: Tue, 11 Nov 2003 15:18:05 +0100 [thread overview]
Message-ID: <3FB0EF9D.8040900@free.fr> (raw)
In-Reply-To: <20031111144426.08e186da.jrydberg@night.trouble.net>
Johan Rydberg wrote:
> Johan Rydberg <jrydberg@night.trouble.net> wrote: (Yes, I did)
>
> : I have yet not figured out a way to alter QEMU to see how much of
> : the execution time these blocks consume. Say that the ~2.38% of
> : the blocks consume 10% of the time, it might be worth doing extra
> : optmizations on then. Fabrice, do you know how I could hack QEMU
> : to get this kind of information?
>
> I disabled chaining and counted each invoking of basic blocks, and
> maintained a separate counter for those blocks that contain internal
> loops. Booting the Debian image to the login prompt gave that the
> blocks with internal loops stod for 33.7% of all invoked blocks.
> Can anyone verify this? (by hacking QEMU yourself, both verifying
> the numbers and that I collect the statistics correctly) It should
> not take more than 20 minutes all together.
I would have done about the same to get the stats :-) I read that wabi
was able to optimize these kind of loops, so I guess it is really
interesting.
> Assume that the values are correct. Then optimization of the blocks
> that contain loops could result in a rather huge performance boost.
> You could for example try to move register stores and loads out of
> the it and just work with host registers in the actual loop.
I don't have time yet to optimize QEMU, but I'll think about that. Of
course if someone does the patch I will accept it !
Fabrice.
prev parent reply other threads:[~2003-11-11 15:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-11 13:14 [Qemu-devel] Basic block statistics Johan Rydberg
2003-11-11 13:44 ` Johan Rydberg
2003-11-11 14:18 ` Fabrice Bellard [this message]
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=3FB0EF9D.8040900@free.fr \
--to=fabrice.bellard@free.fr \
--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).