From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Clemens Kolbitsch <clemens.kol@gmx.at>
Subject: Re: [Qemu-devel] performance monitor
Date: Thu, 3 Jan 2008 22:07:07 +0000 [thread overview]
Message-ID: <200801032207.08448.paul@codesourcery.com> (raw)
In-Reply-To: <200801032238.03458.clemens.kol@gmx.at>
> Does anyone have an idea on how I can measure performance in qemu to a
> somewhat accurate level? I have modified qemu (the memory handling) and the
> linux kernel and want to find out the penalty this introduced... does
> anyone have any comments / ideas on this?
Short answer is you probably can't. And even if you can I won't believe tyour
results unless you've verified them on real hardware :-)
With the exception of some very small embedded cores, Modern CPUs have complex
out of order execution pipelines and multi-level cache hierarchies. It's
common for performance to be dominated by these secondary factors rather than
raw instruction throughput.
Exactly what features dominate performance is very application specific.
Determining which factor dominates is unlikely to be something qemu can help
with.
However if e.g. you know that for your application there's a good correlation
was between performance and L2 cache misses you could instrument qemu to and
a L1/L2 cache model. The overhead will be fairly severe (easily 10x slower),
and completely screw up any realtime measurements. However it would produce
some useful cache use statistics that you could use to guesstimate actual
performance. This is similar to how cachegrind works. Obviously if your
application isn't cache bound then these figures will be meaningless.
Paul
next prev parent reply other threads:[~2008-01-03 22:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-03 20:36 [Qemu-devel] performance monitor Clemens Kolbitsch
2008-01-03 21:29 ` Paul Brook
2008-01-03 21:38 ` Clemens Kolbitsch
2008-01-03 22:07 ` Paul Brook [this message]
2008-01-03 22:11 ` Clemens Kolbitsch
2008-01-03 22:18 ` Paul Brook
2008-01-03 22:21 ` Clemens Kolbitsch
2008-01-03 22:19 ` Laurent Desnogues
2008-01-04 8:49 ` Rob Landley
2008-01-04 15:09 ` Clemens Kolbitsch
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=200801032207.08448.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=clemens.kol@gmx.at \
--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).