qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Laurent Desnogues" <laurent.desnogues@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] performance monitor
Date: Thu, 3 Jan 2008 23:19:29 +0100	[thread overview]
Message-ID: <761ea48b0801031419w7db42f83o7030d7c3e740512e@mail.gmail.com> (raw)
In-Reply-To: <200801032311.24715.clemens.kol@gmx.at>

On Jan 3, 2008 11:11 PM, Clemens Kolbitsch <clemens.kol@gmx.at> wrote:
>
> Well, the measuring I had in mind partly concentrats on TLB misses, page
> faults, etc. (in addition to the cycle measuring). guess i'll have to
> implement something for myself in qemu :-/

There's something not clear here:  do you want to measure your kernel
changes or do you want to profile Qemu?

As Paul clearly explained you can't do both :)

If you want to measure kernel performance oprofile is probably worth
looking at.  But you will need the real hardware.

Another option, though much more intrusive, would be to add explicit
performance counters in places you need to look at (this method can
be applied to both Qemu too).

And to say it again:  nobody can expect to measure OS performance
on a simulator, unless the simulator is directly derived from the HDL
code written by designers.  At least I would never trust such a
result ;)


Laurent

  parent reply	other threads:[~2008-01-03 22:19 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
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 [this message]
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=761ea48b0801031419w7db42f83o7030d7c3e740512e@mail.gmail.com \
    --to=laurent.desnogues@gmail.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).