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:18:58 +0000 [thread overview]
Message-ID: <200801032218.59363.paul@codesourcery.com> (raw)
In-Reply-To: <200801032311.24715.clemens.kol@gmx.at>
> 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 :-/
Be aware that the TLB qemu uses behaves very differently to a real CPU TLB. If
you want to get TLB miss statistics you'll need to model a "real" TLB for
that separately.
Page faults should be straightforward, but any half-decent guest OS would be
able to tell you those anyway.
Paul
next prev 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 [this message]
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=200801032218.59363.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.