From: "Laurent Desnogues" <laurent.desnogues@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Performance Monitoring
Date: Wed, 21 May 2008 08:41:18 +0200 [thread overview]
Message-ID: <761ea48b0805202341y3b598311t24444d8020a1e25a@mail.gmail.com> (raw)
In-Reply-To: <200805202306.45277.paul@codesourcery.com>
On 5/21/08, Paul Brook <paul@codesourcery.com> wrote:
> > get full CPU opcode statistics (how many times
> > every opcode was executed).
...
> You probably already know this, but I'd be surprised if the statistics you get
> have much/any correlation with real world performance on modern hardware.
The OP wants to count instruction opcodes, not cycles or other timing
dependent statistics. Is there something that prevents exact counting
of that?
Laurent
next prev parent reply other threads:[~2008-05-21 6:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-20 18:56 [Qemu-devel] Performance Monitoring Cheif Jones
2008-05-20 22:06 ` Paul Brook
2008-05-21 0:09 ` Vince Weaver
2008-05-21 6:41 ` Laurent Desnogues [this message]
2008-05-20 22:44 ` Stanislav Shwartsman
2008-05-21 16:10 ` [Qemu-devel] " Charles Duffy
2008-05-22 3:46 ` Glauber Costa
2008-05-22 6:13 ` Cheif Jones
2008-05-23 3:38 ` Vince Weaver
2008-05-25 12:22 ` Cheif Jones
2008-05-28 0:21 ` Vince Weaver
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=761ea48b0805202341y3b598311t24444d8020a1e25a@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).