qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Pavel Dovgalyuk" <dovgaluk@ispras.ru>
To: 'Igor R' <boost.lists@gmail.com>,
	'Pavel Dovgalyuk' <Pavel.Dovgaluk@ispras.ru>,
	'QEMU Developers' <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v5 0/7] Deterministic replay extensions
Date: Thu, 17 Mar 2016 11:06:48 +0300	[thread overview]
Message-ID: <000a01d18023$f4d0f280$de72d780$@ru> (raw)
In-Reply-To: <CAPnv1PLXxRaaG6Ur45gopAcNJcJh7tAx15Ra0zaS8K92kFOZYQ@mail.gmail.com>

> From: igor.rubinov@gmail.com [mailto:igor.rubinov@gmail.com] On Behalf Of Igor R
> > This set of patches is related to the reverse execution and deterministic
> > replay of qemu execution. It includes recording and replaying of serial devices
> > and block devices operations.
> 
> Thanks for the great feature.
> 
> A couple of questions:
> * Is it possible to enable/disable recording when QEMU is already
> running? I.e. is it ok to call replay_configure() or replay_enable()
> from the monitor? Would it be possible to replay such a log?

Our internal code base does not include this feature.
But we plan to implement this after submitting all already existing patches.

> * Currently, when running QEMU with the above drive configuration
> (even w/o icount), savevm command doesn't seem to work correctly, and
> subsequent loavm crashes QEMU. Is it just a bug or this feature
> doesn't support snapshots?

Supporting snapshots includes much more work in addition to correct interaction
with replay. Therefore this feature is not supported yet, but we will add it later.

> * The replaying is much slower than the original scenario. Is it
> affected by icount shift? What shift values would allow "real time"
> speed?

icount shows how many guest instructions correspond to one guest clock tick.
"Real speed" may differ from machine to machine.
However, replaying speed was not the subject of our investigations yet.
Recording speed is more important, because it may affect the behavior of the system.

Pavel Dovgalyuk

  reply	other threads:[~2016-03-17  8:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-14  7:44 [Qemu-devel] [PATCH v5 0/7] Deterministic replay extensions Pavel Dovgalyuk
2016-03-14  7:44 ` [Qemu-devel] [PATCH v5 1/7] replay: character devices Pavel Dovgalyuk
2016-03-14 14:11   ` Paolo Bonzini
2016-03-23 15:45   ` Kevin Wolf
2016-03-23 16:54     ` Paolo Bonzini
2016-03-14  7:44 ` [Qemu-devel] [PATCH v5 2/7] icount: remove obsolete warp call Pavel Dovgalyuk
2016-03-14  7:44 ` [Qemu-devel] [PATCH v5 3/7] icount: decouple warp calls Pavel Dovgalyuk
2016-03-14  7:44 ` [Qemu-devel] [PATCH v5 4/7] block: add flush callback Pavel Dovgalyuk
2016-03-23 15:46   ` Kevin Wolf
2016-03-14  7:44 ` [Qemu-devel] [PATCH v5 5/7] replay: bh scheduling fix Pavel Dovgalyuk
2016-03-14  7:45 ` [Qemu-devel] [PATCH v5 6/7] replay: fix error message Pavel Dovgalyuk
2016-03-24 11:56   ` Kevin Wolf
2016-03-14  7:45 ` [Qemu-devel] [PATCH v5 7/7] replay: introduce block devices record/replay Pavel Dovgalyuk
2016-03-23 15:52   ` Kevin Wolf
2016-03-15 20:04 ` [Qemu-devel] [PATCH v5 0/7] Deterministic replay extensions Igor R
2016-03-17  8:06   ` Pavel Dovgalyuk [this message]
2016-03-24 11:59 ` Kevin Wolf
2016-03-24 19:24   ` Pavel Dovgalyuk

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='000a01d18023$f4d0f280$de72d780$@ru' \
    --to=dovgaluk@ispras.ru \
    --cc=Pavel.Dovgaluk@ispras.ru \
    --cc=boost.lists@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).