From: Christopher Covington <cov@codeaurora.org>
To: Anthony Carno <acarno@vt.edu>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Logging number of translated instructions per basic block
Date: Wed, 05 Aug 2015 13:11:39 -0400 [thread overview]
Message-ID: <55C243CB.8080801@codeaurora.org> (raw)
In-Reply-To: <CA+h4_fYWW9nf2D+bse6p4sRBaqPRyRoMZx+_LXZj7P2ZdN7y3A@mail.gmail.com>
Hi Anthony,
On 07/28/2015 05:20 PM, Anthony Carno wrote:
> Hi there,
>
> As the subject of my email suggests, is there a way to log the number of
> translated instructions per basic block? I've dug into the debug code a bit
> (specifically /target_disas /and the arch-specific /print_insn_*/) and haven't
> found anything that would suggest this is doable, but before I go and move on
> to my plan B (which is devising a plan C haha), I'd like to ask and make sure
> I'm not missing something. Thank you!
I just posted a rather unruly (but functional) set of patches with the cover
letter title of "RFC: ARM Semihosting, PMU, and BBV Changes". These changes
include support for collecting block vectors, which are nothing more than
accumulating instruction counts broken per block (and interval). While I would
guess there are probably much better ways to implement the same functionality,
perhaps it's a starting point.
Christopher Covington
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2015-08-05 17:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-28 21:20 [Qemu-devel] Logging number of translated instructions per basic block Anthony Carno
2015-08-05 17:11 ` Christopher Covington [this message]
2015-08-06 18:05 ` Christopher Covington
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=55C243CB.8080801@codeaurora.org \
--to=cov@codeaurora.org \
--cc=acarno@vt.edu \
--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.