* [Qemu-devel] Logging number of translated instructions per basic block
@ 2015-07-28 21:20 Anthony Carno
2015-08-05 17:11 ` Christopher Covington
0 siblings, 1 reply; 3+ messages in thread
From: Anthony Carno @ 2015-07-28 21:20 UTC (permalink / raw)
To: qemu-devel
[-- Attachment #1: Type: text/plain, Size: 464 bytes --]
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!
Respectfully,
Anthony Carno
[-- Attachment #2: Type: text/html, Size: 531 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Qemu-devel] Logging number of translated instructions per basic block
2015-07-28 21:20 [Qemu-devel] Logging number of translated instructions per basic block Anthony Carno
@ 2015-08-05 17:11 ` Christopher Covington
2015-08-06 18:05 ` Christopher Covington
0 siblings, 1 reply; 3+ messages in thread
From: Christopher Covington @ 2015-08-05 17:11 UTC (permalink / raw)
To: Anthony Carno, qemu-devel
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Qemu-devel] Logging number of translated instructions per basic block
2015-08-05 17:11 ` Christopher Covington
@ 2015-08-06 18:05 ` Christopher Covington
0 siblings, 0 replies; 3+ messages in thread
From: Christopher Covington @ 2015-08-06 18:05 UTC (permalink / raw)
To: Anthony Carno, qemu-devel
On 08/05/2015 01:11 PM, Christopher Covington wrote:
> 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!
Perhaps a better answer than my previous one is cpu_get_ticks() when -icount
is used:
https://lists.gnu.org/archive/html/qemu-devel/2015-05/msg00162.html
Christopher Covington
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2015-08-06 18:05 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-07-28 21:20 [Qemu-devel] Logging number of translated instructions per basic block Anthony Carno
2015-08-05 17:11 ` Christopher Covington
2015-08-06 18:05 ` Christopher Covington
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).