From: Steffen Liebergeld <usenet@gmx.eu>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: Precise guest instruction count.
Date: Wed, 11 Mar 2009 12:53:53 +0000 (UTC) [thread overview]
Message-ID: <gp8c91$g22$1@ger.gmane.org> (raw)
In-Reply-To: 761ea48b0903110342i3317f650hd00302ca47bf9843@mail.gmail.com
Hi,
Laurent Desnogues <laurent.desnogues@gmail.com> schrieb:
> On Wed, Mar 11, 2009 at 11:33 AM, Steffen Liebergeld <usenet@gmx.eu> wrote:
>> I temporarily disabled timers in Qemu, so normally time should not
>> influence my measurements.
>
> As Paul explained, in system mode there are other things that
> can cause interrupts, which you can't disable (unless you have
> your own emulated OS).
I am interested in which interrupts might occur, and how they influence the
instruction count. I am not using any input, and all output is sent to the
serial port via "-serial stdout".
I have a small assembler loop like the following pseudo code:
NOP
mov R1, $1000
loop:
subs R1, $1
bne loop
NOP
On every NOP Qemu prints the instruction count.
By turning of all timers in Qemu I hope to disable all timer interrupts for
the guest. The results I get are not correct for the first time the code is
run, but for all subsequent runs. In the first run, the instruction count has
12 additional instructions, which are not actually executed.
What is the cause of those additional instructions?
Greetings, Steffen
next prev parent reply other threads:[~2009-03-11 12:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-09 9:38 [Qemu-devel] Precise guest instruction count Steffen Liebergeld
2009-03-09 21:56 ` Laurent Desnogues
2009-03-11 10:33 ` [Qemu-devel] " Steffen Liebergeld
2009-03-11 10:42 ` Laurent Desnogues
2009-03-11 12:53 ` Steffen Liebergeld [this message]
2009-03-11 13:13 ` Paul Brook
2009-03-10 1:55 ` [Qemu-devel] " Paul Brook
2009-03-11 11:45 ` [Qemu-devel] " Steffen Liebergeld
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='gp8c91$g22$1@ger.gmane.org' \
--to=usenet@gmx.eu \
--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).