qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Cheif Jones" <avivgnet@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: Performance Monitoring
Date: Thu, 22 May 2008 09:13:44 +0300	[thread overview]
Message-ID: <3000d2e90805212313r3c3fbaf0laabb4074f6cb52e7@mail.gmail.com> (raw)
In-Reply-To: <5d6222a80805212046l5c3e6f38q381656abf7a1f613@mail.gmail.com>

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

Hi All,

Thanks for all the good advice!

I do not have the HW and so I need an emulator. Also the target arch is not
x86, it has to be some RISC (ARM, PPC).

I would like to run an OS, say Linux, and take a sample for a small period
of time (seconds) while some app(s) are running and get a list of opcode
names and how many times they were executed. I'm not interested in CPI at
the moment.

Vince, I briefly read your paper and went through the patch . It is very
interesting and maybe i can use it for what i need. Questions:

   - Is there a 1-1 correspondence between a BBV and a target CPU opcode?
   - If i use the QEMU to generate BBVs, and the other tools you mentioned
   that gets BBV as input, will i be able to see the opcode name (and not just
   a uniqe ID that goes with BBV)
   - Paul mentioned "With either alternative you'll still have issues with
   exceptions. MMU faults abort a TB early, so will screw up your statistics.
   One possibility is to terminate a TB on every memory access, like we do for
   watchpoints." - is this an issue addressed by your patch?

Thanks,
Chief

   -

   -


On 5/22/08, Glauber
>
>
> >> 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."
>
>
>

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

  reply	other threads:[~2008-05-22  6:13 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
2008-05-22  6:13     ` Cheif Jones [this message]
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=3000d2e90805212313r3c3fbaf0laabb4074f6cb52e7@mail.gmail.com \
    --to=avivgnet@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).