From: Jamie Lokier <jamie@shareable.org>
To: Sami Kiminki <sami.kiminki@tkk.fi>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Instruction counting instrumentation for ARM, 2nd version
Date: Fri, 12 Jun 2009 16:41:25 +0100 [thread overview]
Message-ID: <20090612154125.GD18247@shareable.org> (raw)
In-Reply-To: <1244804168.7242.186.camel@dis>
Sami Kiminki wrote:
> What we would really like to see is a more general instrumentation
> framework, not just instruction counting and not just for ARM targets.
> The reason for this is that many measurements are so much easier to do
> in emulated/simulated environment than in real HW (e.g. instruction
> counting) and doing them in QEMU is way faster than using an ISA
> interpreter such as Valgrind. Some other instrumentation examples that
> come to my mind are cache usage efficiency analysis, branch profiling,
> and naturally instruction and memory access tracing.
Valgrind isn't an interpreter. It's a JIT compiler like QEMU's TCG,
so are you sure these things are way faster in QEMU?
What might work better would be to share some code from Valgrind/Cachegrind.
-- Jamie
next prev parent reply other threads:[~2009-06-12 15:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 10:56 [Qemu-devel] [PATCH] Instruction counting instrumentation for ARM, 2nd version Sami Kiminki
2009-06-12 15:41 ` Jamie Lokier [this message]
2009-06-15 8:12 ` Sami Kiminki
2009-06-15 13:26 ` Laurent Desnogues
2009-06-29 8:42 ` [Qemu-devel] [PATCH] Instruction counting instrumentation for ARM v3 Sami Kiminki
[not found] ` <761ea48b0906150531j6cf88fa2v5652322efcc7469c@mail.gmail.com>
2009-06-15 13:31 ` [Qemu-devel] [PATCH] Instruction counting instrumentation for ARM, 2nd version & 2nd try Sami Kiminki
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=20090612154125.GD18247@shareable.org \
--to=jamie@shareable.org \
--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).