From: Paolo Bonzini <pbonzini@redhat.com>
To: Pavel Dovgalyuk <pavel.dovgaluk@ispras.ru>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, peter.maydell@linaro.org, mst@redhat.com,
jasowang@redhat.com, quintela@redhat.com, kraxel@redhat.com
Subject: Re: [Qemu-devel] [PATCH v9 06/10] replay: fix save/load vm for non-empty queue
Date: Thu, 4 May 2017 12:31:42 +0200 [thread overview]
Message-ID: <b365904f-21ae-85a7-a3a6-bbe21c62e35a@redhat.com> (raw)
In-Reply-To: <20170504084210.7488.37561.stgit@PASHA-ISP>
On 04/05/2017 10:42, Pavel Dovgalyuk wrote:
> From: Pavel Dovgalyuk <Pavel.Dovgaluk@ispras.ru>
>
> This patch does not allows saving/loading vmstate when
> replay events queue is not empty. There is no reliable
> way to save events queue, because it describes internal
> coroutine state. Therefore saving and loading operations
> should be deferred to another record/replay step.
Can it actually be non-empty after bdrv_drain_all?
Paolo
> Signed-off-by: Pavel Dovgalyuk <pavel.dovgaluk@ispras.ru>
> ---
> include/sysemu/replay.h | 3 +++
> migration/savevm.c | 13 +++++++++++++
> replay/replay-snapshot.c | 6 ++++++
> 3 files changed, 22 insertions(+)
>
> diff --git a/include/sysemu/replay.h b/include/sysemu/replay.h
> index f1c0712795..5c9db2a2ef 100644
> --- a/include/sysemu/replay.h
> +++ b/include/sysemu/replay.h
> @@ -164,5 +164,8 @@ void replay_audio_in(int *recorded, void *samples, int *wpos, int size);
> /*! Called at the start of execution.
> Loads or saves initial vmstate depending on execution mode. */
> void replay_vmstate_init(void);
> +/*! Called to ensure that replay state is consistent and VM snapshot
> + can be created */
> +bool replay_can_snapshot(void);
>
> #endif
> diff --git a/migration/savevm.c b/migration/savevm.c
> index 03ae1bdeb4..358d22170d 100644
> --- a/migration/savevm.c
> +++ b/migration/savevm.c
> @@ -54,6 +54,7 @@
> #include "qemu/cutils.h"
> #include "io/channel-buffer.h"
> #include "io/channel-file.h"
> +#include "sysemu/replay.h"
>
> #ifndef ETH_P_RARP
> #define ETH_P_RARP 0x8035
> @@ -2083,6 +2084,12 @@ int save_vmstate(Monitor *mon, const char *name)
> Error *local_err = NULL;
> AioContext *aio_context;
>
> + if (!replay_can_snapshot()) {
> + monitor_printf(mon, "Record/replay does not allow making snapshot right now. "
> + "Try stopping at another step.\n");
> + return ret;
> + }
> +
> if (!bdrv_all_can_snapshot(&bs)) {
> monitor_printf(mon, "Device '%s' is writable but does not "
> "support snapshots.\n", bdrv_get_device_name(bs));
> @@ -2244,6 +2251,12 @@ int load_vmstate(const char *name)
> AioContext *aio_context;
> MigrationIncomingState *mis = migration_incoming_get_current();
>
> + if (!replay_can_snapshot()) {
> + error_report("Record/replay does not allow loading snapshot right now. "
> + "Try stopping at another step.\n");
> + return -EINVAL;
> + }
> +
> if (!bdrv_all_can_snapshot(&bs)) {
> error_report("Device '%s' is writable but does not support snapshots.",
> bdrv_get_device_name(bs));
> diff --git a/replay/replay-snapshot.c b/replay/replay-snapshot.c
> index 65e2d375c2..438d82ec33 100644
> --- a/replay/replay-snapshot.c
> +++ b/replay/replay-snapshot.c
> @@ -76,3 +76,9 @@ void replay_vmstate_init(void)
> }
> }
> }
> +
> +bool replay_can_snapshot(void)
> +{
> + return replay_mode == REPLAY_MODE_NONE
> + || !replay_has_events();
> +}
>
next prev parent reply other threads:[~2017-05-04 10:31 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 8:41 [Qemu-devel] [PATCH v9 00/10] replay additions Pavel Dovgalyuk
2017-05-04 8:41 ` [Qemu-devel] [PATCH v9 01/10] block: implement bdrv_snapshot_goto for blkreplay Pavel Dovgalyuk
2017-05-04 8:41 ` [Qemu-devel] [PATCH v9 02/10] blkreplay: create temporary overlay for underlaying devices Pavel Dovgalyuk
2017-05-04 8:41 ` [Qemu-devel] [PATCH v9 03/10] replay: disable default snapshot for record/replay Pavel Dovgalyuk
2017-05-04 8:41 ` [Qemu-devel] [PATCH v9 04/10] replay: fix processing async events Pavel Dovgalyuk
2017-05-04 10:30 ` Paolo Bonzini
2017-05-04 12:32 ` Pavel Dovgalyuk
2017-05-04 8:42 ` [Qemu-devel] [PATCH v9 05/10] replay: fixed replay_enable_events Pavel Dovgalyuk
2017-05-04 8:42 ` [Qemu-devel] [PATCH v9 06/10] replay: fix save/load vm for non-empty queue Pavel Dovgalyuk
2017-05-04 9:33 ` Juan Quintela
2017-05-04 10:03 ` Pavel Dovgalyuk
2017-05-04 10:31 ` Paolo Bonzini [this message]
2017-05-04 11:13 ` Pavel Dovgalyuk
2017-05-04 11:52 ` Paolo Bonzini
2017-05-04 11:54 ` Pavel Dovgalyuk
2017-05-04 12:02 ` Paolo Bonzini
2017-05-04 12:10 ` Pavel Dovgalyuk
2017-05-04 12:32 ` Paolo Bonzini
2017-05-04 12:34 ` Pavel Dovgalyuk
2017-05-04 12:52 ` Paolo Bonzini
2017-05-04 13:02 ` Pavel Dovgalyuk
2017-05-04 13:12 ` Paolo Bonzini
2017-05-04 13:24 ` Pavel Dovgalyuk
2017-05-04 8:42 ` [Qemu-devel] [PATCH v9 07/10] replay: added replay log format description Pavel Dovgalyuk
2017-05-04 8:42 ` [Qemu-devel] [PATCH v9 08/10] replay: make safe vmstop at record/replay Pavel Dovgalyuk
2017-05-04 8:42 ` [Qemu-devel] [PATCH v9 09/10] replay: save prior value of the host clock Pavel Dovgalyuk
2017-05-04 8:42 ` [Qemu-devel] [PATCH v9 10/10] icount: fixed saving/restoring of icount warp timers Pavel Dovgalyuk
2017-05-04 9:35 ` [Qemu-devel] [PATCH v9 00/10] replay additions no-reply
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=b365904f-21ae-85a7-a3a6-bbe21c62e35a@redhat.com \
--to=pbonzini@redhat.com \
--cc=jasowang@redhat.com \
--cc=kraxel@redhat.com \
--cc=kwolf@redhat.com \
--cc=mst@redhat.com \
--cc=pavel.dovgaluk@ispras.ru \
--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).