qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Glauber Costa" <glommer@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: Performance Monitoring
Date: Thu, 22 May 2008 00:46:44 -0300	[thread overview]
Message-ID: <5d6222a80805212046l5c3e6f38q381656abf7a1f613@mail.gmail.com> (raw)
In-Reply-To: <g11hhk$99u$1@ger.gmane.org>

On Wed, May 21, 2008 at 1:10 PM, Charles Duffy
<Charles_Duffy@messageone.com> wrote:
> Cheif Jones wrote:
>>
>> I'm doing a research project in which i want to run an OS under an
>> emulator for a period of time and get full CPU opcode statistics (how many
>> times every opcode was executed). As far as i understand the Qemu design, it
>> is doing "JIT" translation of terget opcode to host opcodes to improve
>> performance, and so there is no easy way to count target opcodes (e.g a loop
>> is compiled JIT and runs natively).
>
> Is an actual emulator necessary, or could you use something like an
> instrumented UML kernel? I'd think that would be a much simpler approach.

Since he claims to need opcode statistics, and UML won't trap any
instruction but the privileged ones, does not seem feasible.

-- 
Glauber Costa.
"Free as in Freedom"
http://glommer.net

"The less confident you are, the more serious you have to act."

  reply	other threads:[~2008-05-22  3:46 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
2008-05-20 22:44 ` Stanislav Shwartsman
2008-05-21 16:10 ` [Qemu-devel] " Charles Duffy
2008-05-22  3:46   ` Glauber Costa [this message]
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=5d6222a80805212046l5c3e6f38q381656abf7a1f613@mail.gmail.com \
    --to=glommer@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).