From: Peter Maydell <peter.maydell@linaro.org>
To: Ayaz Akram <aaqemu@gmail.com>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Executed Host Instructions
Date: Tue, 28 Jun 2016 12:17:52 +0100 [thread overview]
Message-ID: <CAFEAcA9AGEPfGRTEQnp0fKKPScoPgB7kQn5WbefORNPih--qfw@mail.gmail.com> (raw)
In-Reply-To: <878txpd1u7.fsf@fimbulvetr.bsc.es>
On 28 June 2016 at 11:50, Lluís Vilanova <vilanova@ac.upc.edu> wrote:
> Ayaz Akram writes:
>
>> Hi All,
>> I want to count number of host instructions (only for guest code) executed
>> when qemu emulates an application. I wonder if helper functions are
>> supported with tcg back end as well, which can be a possible solution for
>> the mentioned problem ? If not, is there any other solution in someone's
>> mind ?
>
> If you don't care about helpers, you can use QEMU's log functionality (-d
> out_asm).
Note that this doesn't directly count instructions -- it only
displays the assembly at translate time, and you'd then have
to calculate the actual executions based on -d exec logging,
and adjust it to deal with exceptions.
It ought to be possible to use the icount machinery to trace
instruction execution counts, but we don't do it today.
thanks
-- PMM
next prev parent reply other threads:[~2016-06-28 11:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-27 21:50 [Qemu-devel] Executed Host Instructions Ayaz Akram
2016-06-28 10:50 ` Lluís Vilanova
2016-06-28 11:17 ` Peter Maydell [this message]
2016-06-28 15:24 ` Ayaz Akram
2016-06-28 15:28 ` Peter Maydell
2016-06-28 15:53 ` Ayaz Akram
2016-06-28 15:56 ` Peter Maydell
2016-06-30 1:13 ` Ayaz Akram
2016-06-30 7:00 ` Peter Maydell
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=CAFEAcA9AGEPfGRTEQnp0fKKPScoPgB7kQn5WbefORNPih--qfw@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=aaqemu@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).