From: "felix.matenaar@rwth-aachen" <felix.matenaar@rwth-aachen.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU timing requirements
Date: Sun, 26 Jun 2011 00:29:17 +0200 [thread overview]
Message-ID: <4E06613D.8020603@rwth-aachen.de> (raw)
In-Reply-To: <BANLkTikSK+yVEeYwHdMsitJK9CGLzfn0wA@mail.gmail.com>
On 06/25/2011 10:02 PM, Mulyadi Santosa wrote:
> On Sat, Jun 25, 2011 at 23:28, felix.matenaar@rwth-aachen
> <felix.matenaar@rwth-aachen.de> wrote:
>> No. What I do is using gen_helper_ to compile hooks into call/ret/jmp and
>> memory access. The Heuristics can then hook the events so calculation is
>> done during the execution of a basic block. I thought that it could be
>> possible that Qemu sets a timeout for BBL execution to prevent CPU
>> monopolization by e.g. a long sequence of rep. That would make sense because
>> my heuristics calculation time falls into the BBL execution time for Qemu.
>> Does anyone know more about that?
> perhaps your heuristics code somehow coincide with the timer alarm
> (PIT, HPET etc) emulation in Qemu....and somewhere your code is not
> reentrant.....
>
Think I found the problem. It was a bug in my code and because of some
weird circumstances, backtrace and addresses seemed to be a segfault in
a BBL.
next prev parent reply other threads:[~2011-06-25 22:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-25 2:34 [Qemu-devel] QEMU timing requirements felix.matenaar@rwth-aachen
2011-06-25 4:26 ` Mulyadi Santosa
2011-06-25 16:28 ` felix.matenaar@rwth-aachen
2011-06-25 20:02 ` Mulyadi Santosa
2011-06-25 22:29 ` felix.matenaar@rwth-aachen [this message]
2011-06-26 4:49 ` Mulyadi Santosa
2011-06-26 17:49 ` felix.matenaar@rwth-aachen
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=4E06613D.8020603@rwth-aachen.de \
--to=felix.matenaar@rwth-aachen.de \
--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).