qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Desnogues <laurent.desnogues@gmail.com>
To: Sami Kiminki <sami.kiminki@tkk.fi>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] POLL: Support for instrumentation?
Date: Fri, 19 Jun 2009 08:46:56 +0200	[thread overview]
Message-ID: <761ea48b0906182346u5d05c1dev323acd98432638@mail.gmail.com> (raw)
In-Reply-To: <1245336842.32163.18.camel@dis>

On Thu, Jun 18, 2009 at 4:54 PM, Sami Kiminki<sami.kiminki@tkk.fi> wrote:
>
> We are considering doing some work on instrumentation support for QEMU.
> But before rushing into implementation, I wonder if there is more
> general interest in this subject, and if so, what kind of
> instrumentation would you like to see?

I am definitely interested. But again, being the less intrusive
possible is a must from my point of view. Not degrading
performance too much is also a must.

Things I'd like to see:

- instruction traces (including category mix)
- memory traces
- canceled conditional instructions
- taken/non taken branches
- flexible branch prediction
- flexible multi-level cache simulation

Some of these things can be done after execution, provided
enough information is collected at runtime.  By flexible, I mean
an easy to change for instance predictor(s) and cache
geometry.

This is a huge subject with a huge literature :-)

>From an implementation point of view, doing it so that it is
easy to add runtime info collection and post execution
info extraction will be difficult, especially if you want it to
be accepted into mainline.


Laurent

      parent reply	other threads:[~2009-06-19  6:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-18 14:54 [Qemu-devel] POLL: Support for instrumentation? Sami Kiminki
2009-06-18 16:00 ` Luis Useche
2009-06-19  6:46 ` Laurent Desnogues [this message]

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=761ea48b0906182346u5d05c1dev323acd98432638@mail.gmail.com \
    --to=laurent.desnogues@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sami.kiminki@tkk.fi \
    /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).