qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Pavel Dovgalyuk" <dovgaluk@ispras.ru>
To: 'Paolo Bonzini' <pbonzini@redhat.com>,
	'Pavel Dovgalyuk' <pavel.dovgaluk@ispras.ru>,
	qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, jasowang@redhat.com,
	quintela@redhat.com, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH v4 2/8] replay: save/load initial state
Date: Wed, 21 Sep 2016 18:49:05 +0300	[thread overview]
Message-ID: <004901d2141f$af552420$0dff6c60$@ru> (raw)
In-Reply-To: <5d38dfa7-8a5f-a324-ad22-cdd56d288697@redhat.com>

> From: Paolo Bonzini [mailto:pbonzini@redhat.com]
> On 21/09/2016 13:33, Pavel Dovgalyuk wrote:
> > +New VM snapshots may be created in replay mode. They can be used later
> > +to recover the desired VM state. All VM states created in replay mode
> > +are associated with the moment of time in the replay scenario.
> > +After recovering the VM state replay will start from that position.
> > +
> > +Default starting snapshot name may be specified with icount field
> > +rrsnapshot as follows:
> > + -icount shift=7,rr=record,rrfile=replay.bin,rrsnapshot=snapshot_name
> > +
> > +This snapshot is created at start of recording and restored at start
> > +of replaying. It also can be loaded while replaying to roll back
> > +the execution.
> 
> Should you mention somewhere that you need -snapshot for raw images?

Do you mean when rrsnapshot is used with raw images?
I'll update the docs.

Pavel Dovgalyuk

  reply	other threads:[~2016-09-21 15:49 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-21 11:33 [Qemu-devel] [PATCH v4 0/8] replay additions Pavel Dovgalyuk
2016-09-21 11:33 ` [Qemu-devel] [PATCH v4 1/8] record/replay: add network support Pavel Dovgalyuk
2016-09-23  6:06   ` Jason Wang
2016-09-23  7:52     ` Pavel Dovgalyuk
2016-10-13  8:01     ` Pavel Dovgalyuk
2016-09-21 11:33 ` [Qemu-devel] [PATCH v4 2/8] replay: save/load initial state Pavel Dovgalyuk
2016-09-21 15:39   ` Paolo Bonzini
2016-09-21 15:49     ` Pavel Dovgalyuk [this message]
2016-09-21 15:57       ` Paolo Bonzini
2016-09-22  5:37         ` Pavel Dovgalyuk
2016-09-22  8:51           ` Paolo Bonzini
2016-09-21 11:33 ` [Qemu-devel] [PATCH v4 3/8] block: don't make snapshots for filters Pavel Dovgalyuk
2016-09-21 15:37   ` Paolo Bonzini
2016-09-22  5:43     ` Pavel Dovgalyuk
2016-09-21 11:33 ` [Qemu-devel] [PATCH v4 4/8] block: implement bdrv_recurse_is_first_non_filter for blkreplay Pavel Dovgalyuk
2016-09-21 11:33 ` [Qemu-devel] [PATCH v4 5/8] replay: move internal data to the structure Pavel Dovgalyuk
2016-09-21 11:33 ` [Qemu-devel] [PATCH v4 6/8] replay: vmstate for replay module Pavel Dovgalyuk
2016-09-21 11:33 ` [Qemu-devel] [PATCH v4 7/8] replay: allow replay stopping and restarting Pavel Dovgalyuk
2016-09-21 11:33 ` [Qemu-devel] [PATCH v4 8/8] integratorcp: adding vmstate for save/restore Pavel Dovgalyuk
2016-09-21 15:40 ` [Qemu-devel] [PATCH v4 0/8] replay additions Paolo Bonzini
2016-09-22  5:41   ` Pavel Dovgalyuk
2016-09-22  8:51     ` Paolo Bonzini

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='004901d2141f$af552420$0dff6c60$@ru' \
    --to=dovgaluk@ispras.ru \
    --cc=jasowang@redhat.com \
    --cc=mst@redhat.com \
    --cc=pavel.dovgaluk@ispras.ru \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    /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).