qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Dovgalyuk <Pavel.Dovgaluk@ispras.ru>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, peter.maydell@linaro.org,
	boost.lists@gmail.com, quintela@redhat.com, jasowang@redhat.com,
	mst@redhat.com, zuban32s@gmail.com,
	maria.klimushenkova@ispras.ru, dovgaluk@ispras.ru,
	kraxel@redhat.com, pavel.dovgaluk@ispras.ru, pbonzini@redhat.com,
	alex.bennee@linaro.org
Subject: [Qemu-devel] [RFC PATCH v5 20/24] replay: avoid recursive call of checkpoints
Date: Tue, 23 Jan 2018 11:55:11 +0300	[thread overview]
Message-ID: <20180123085511.3419.50152.stgit@pasha-VirtualBox> (raw)
In-Reply-To: <20180123085319.3419.97865.stgit@pasha-VirtualBox>

This patch adds a flag which denies recursive call of replay_checkpoint
function. Checkpoints may be accompanied by the hardware events. When event
is processed, virtual device may invoke timer modification functions that
also invoke the checkpoint function. This leads to infinite loop.

Signed-off-by: Pavel Dovgalyuk <pavel.dovgaluk@ispras.ru>
---
 replay/replay.c |   14 +++++++++++++-
 1 file changed, 13 insertions(+), 1 deletion(-)

diff --git a/replay/replay.c b/replay/replay.c
index 585c5de..c676dd4 100644
--- a/replay/replay.c
+++ b/replay/replay.c
@@ -176,13 +176,24 @@ void replay_shutdown_request(ShutdownCause cause)
 bool replay_checkpoint(ReplayCheckpoint checkpoint)
 {
     bool res = false;
+    static bool in_checkpoint;
     assert(EVENT_CHECKPOINT + checkpoint <= EVENT_CHECKPOINT_LAST);
-    replay_save_instructions();
 
     if (!replay_file) {
         return true;
     }
 
+    if (in_checkpoint) {
+        /* If we are already in checkpoint, then there is no need
+           for additional synchronization.
+           Recursion occurs when HW event modifies timers.
+           Timer modification may invoke the checkpoint and
+           proceed to recursion. */
+        return true;
+    }
+    in_checkpoint = true;
+
+    replay_save_instructions();
 
     if (replay_mode == REPLAY_MODE_PLAY) {
         g_assert(replay_mutex_locked());
@@ -204,6 +215,7 @@ bool replay_checkpoint(ReplayCheckpoint checkpoint)
         res = true;
     }
 out:
+    in_checkpoint = false;
     return res;
 }
 

  parent reply	other threads:[~2018-01-23  8:55 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-23  8:53 [Qemu-devel] [RFC PATCH v5 00/24] replay additions Pavel Dovgalyuk
2018-01-23  8:53 ` [Qemu-devel] [RFC PATCH v5 01/24] cpu-exec: fix exception_index handling Pavel Dovgalyuk
2018-01-23  8:53 ` [Qemu-devel] [RFC PATCH v5 02/24] block: implement bdrv_snapshot_goto for blkreplay Pavel Dovgalyuk
2018-01-23  8:53 ` [Qemu-devel] [RFC PATCH v5 03/24] blkreplay: create temporary overlay for underlaying devices Pavel Dovgalyuk
2018-01-23  8:53 ` [Qemu-devel] [RFC PATCH v5 04/24] replay: disable default snapshot for record/replay Pavel Dovgalyuk
2018-01-23  8:53 ` [Qemu-devel] [RFC PATCH v5 05/24] replay: fix processing async events Pavel Dovgalyuk
2018-01-23  8:53 ` [Qemu-devel] [RFC PATCH v5 06/24] replay: fixed replay_enable_events Pavel Dovgalyuk
2018-01-23  8:53 ` [Qemu-devel] [RFC PATCH v5 07/24] replay: fix save/load vm for non-empty queue Pavel Dovgalyuk
2018-01-23  8:54 ` [Qemu-devel] [RFC PATCH v5 08/24] replay: added replay log format description Pavel Dovgalyuk
2018-01-23  8:54 ` [Qemu-devel] [RFC PATCH v5 09/24] replay: save prior value of the host clock Pavel Dovgalyuk
2018-01-23  8:54 ` [Qemu-devel] [RFC PATCH v5 10/24] target/arm/arm-powertctl: drop BQL assertions Pavel Dovgalyuk
2018-01-23  8:54 ` [Qemu-devel] [RFC PATCH v5 11/24] cpus: push BQL lock to qemu_*_wait_io_event Pavel Dovgalyuk
2018-01-23  8:54 ` [Qemu-devel] [RFC PATCH v5 12/24] hax: remove BQL lock/unlock Pavel Dovgalyuk
2018-01-23  8:54 ` [Qemu-devel] [RFC PATCH v5 13/24] kvm: " Pavel Dovgalyuk
2018-01-31  1:24   ` Paolo Bonzini
2018-01-23  8:54 ` [Qemu-devel] [RFC PATCH v5 14/24] replay/replay.c: bump REPLAY_VERSION again Pavel Dovgalyuk
2018-01-23  8:54 ` [Qemu-devel] [RFC PATCH v5 15/24] replay/replay-internal.c: track holding of replay_lock Pavel Dovgalyuk
2018-01-23  8:54 ` [Qemu-devel] [RFC PATCH v5 16/24] replay: make locking visible outside replay code Pavel Dovgalyuk
2018-01-23  8:54 ` [Qemu-devel] [RFC PATCH v5 17/24] replay: push replay_mutex_lock up the call tree Pavel Dovgalyuk
2018-01-23  8:55 ` [Qemu-devel] [RFC PATCH v5 18/24] replay: don't destroy mutex at exit Pavel Dovgalyuk
2018-01-23  8:55 ` [Qemu-devel] [RFC PATCH v5 19/24] replay: check return values of fwrite Pavel Dovgalyuk
2018-01-23  8:55 ` Pavel Dovgalyuk [this message]
2018-01-23  8:55 ` [Qemu-devel] [RFC PATCH v5 21/24] scripts/replay-dump.py: replay log dumper Pavel Dovgalyuk
2018-01-23  8:55 ` [Qemu-devel] [RFC PATCH v5 22/24] replay: don't process async events when warping the clock Pavel Dovgalyuk
2018-01-23  8:55 ` [Qemu-devel] [RFC PATCH v5 23/24] replay: save vmstate of the asynchronous events Pavel Dovgalyuk
2018-01-23  8:55 ` [Qemu-devel] [RFC PATCH v5 24/24] replay: don't drain/flush bdrv queue while RR is working Pavel Dovgalyuk
2018-01-23  9:32 ` [Qemu-devel] [RFC PATCH v5 00/24] replay additions no-reply
2018-01-30  5:57 ` 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=20180123085511.3419.50152.stgit@pasha-VirtualBox \
    --to=pavel.dovgaluk@ispras.ru \
    --cc=alex.bennee@linaro.org \
    --cc=boost.lists@gmail.com \
    --cc=dovgaluk@ispras.ru \
    --cc=jasowang@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=maria.klimushenkova@ispras.ru \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=zuban32s@gmail.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).