All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stanislav Shwartsman" <stlintel@gmail.com>
To: qemu-devel@nongnu.org
Subject: RE: [Qemu-devel] Performance Monitoring
Date: Wed, 21 May 2008 00:44:57 +0200	[thread overview]
Message-ID: <000301c8bacb$229310d0$67b93270$@com> (raw)
In-Reply-To: <3000d2e90805201156g30050a68ve9187e3b94341e99@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 836 bytes --]

Hello,

 

I think it is better to use Bochs for such purpose .

 

Stanislav

 

From: qemu-devel-bounces+stlintel=gmail.com@nongnu.org
[mailto:qemu-devel-bounces+stlintel=gmail.com@nongnu.org] On Behalf Of Cheif
Jones
Sent: Tuesday, May 20, 2008 8:56 PM
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Performance Monitoring

 

Hi All,

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 it possible to disable Qemu's JIT capabilities and get target opcode
statistics?

Cheif


[-- Attachment #2: Type: text/html, Size: 3711 bytes --]

  parent reply	other threads:[~2008-05-20 21:45 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 [this message]
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='000301c8bacb$229310d0$67b93270$@com' \
    --to=stlintel@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 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.