qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Pavel Dovgaluk" <Pavel.Dovgaluk@ispras.ru>
To: 'Paul Brook' <paul@codesourcery.com>, qemu-devel@nongnu.org
Subject: RE: [Qemu-devel] Deterministic replay
Date: Wed, 22 Dec 2010 15:43:12 +0300	[thread overview]
Message-ID: <002501cba1d5$cbe01f40$63a05dc0$@Dovgaluk@ispras.ru> (raw)
In-Reply-To: <201012221235.14145.paul@codesourcery.com>

> >  I am working on implementation of deteministic execution replay
> technology
> > for Qemu. It should be similar to VMWare's replay debugging.
> >
> >  To make alarm timer (which invokes host_alarm_handler function)
> > determinisic, I changed it's behavior: it sets flag, that execution
> should
> > be stopped and this flag is checked before every instruction in the
> > translated code.
> 
> You don't need to do this. A much better solution is to not use the
> host timer
> at all. See -icount.

 Thank you for your reply. 
 I know, that there is a virtual timers, that are enabled by -icount option
and can be used to get rid of host timers usage.
 But the problem is different - I need to synchronize alarm thread, which
breaks the execution of guest code to allow processing interrupts and
interaction with VNC/GDB/...
 Events caused by alarm thread are non-deterministic and asynchronous. To
save these events in the execution log (for latter replay) I need to
synchronize them with execution of guest code.
 The way which I am using for it is allowing execution stop at any point of
the guest code.


Pavel Dovgaluk

      reply	other threads:[~2010-12-22 12:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-22 11:20 [Qemu-devel] Deterministic replay Pavel Dovgaluk
2010-12-22 12:35 ` Paul Brook
2010-12-22 12:43   ` Pavel Dovgaluk [this message]

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='002501cba1d5$cbe01f40$63a05dc0$@Dovgaluk@ispras.ru' \
    --to=pavel.dovgaluk@ispras.ru \
    --cc=paul@codesourcery.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).