qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Dovgalyuk <Pavel.Dovgaluk@ispras.ru>
To: qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, maria.klimushenkova@ispras.ru,
	dovgaluk@ispras.ru, pavel.dovgaluk@ispras.ru
Subject: [Qemu-devel] [PATCH] timer: fix record/replay timerlist probe
Date: Tue, 10 Apr 2018 16:15:50 +0300	[thread overview]
Message-ID: <20180410131550.20064.30595.stgit@pasha-VirtualBox> (raw)

Ciro Santilli reported that commit a5ed352596a8b7eb2f9acce34371b944ac3056c4
breaks the execution replay. It happens due to the probing the clock
for the new instances of iothread. Probing of the timerlists' clock
instead of using them for the deadlines calculation is critical for the replay.
However, this probing was made for the timer lists that are empty.
In record mode such lists are not used for the deadlines and corresponding
clock does not queried.
Therefore this patch disables quering the clock for the empty timerlists
and disabled clocks.

Signed-off-by: Pavel Dovgalyuk <Pavel.Dovgaluk@ispras.ru>
---
 util/qemu-timer.c |    5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/util/qemu-timer.c b/util/qemu-timer.c
index 2ed1bf2..e1c703c 100644
--- a/util/qemu-timer.c
+++ b/util/qemu-timer.c
@@ -587,7 +587,10 @@ int64_t timerlistgroup_deadline_ns(QEMUTimerListGroup *tlg)
             } else {
                 /* Read clock from the replay file and
                    do not calculate the deadline, based on virtual clock. */
-                qemu_clock_get_ns(type);
+                if (atomic_read(&tlg->tl[type]->active_timers)
+                    && tlg->tl[type]->clock->enabled) {
+                    qemu_clock_get_ns(type);
+                }
             }
         }
     }

                 reply	other threads:[~2018-04-10 13:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20180410131550.20064.30595.stgit@pasha-VirtualBox \
    --to=pavel.dovgaluk@ispras.ru \
    --cc=dovgaluk@ispras.ru \
    --cc=maria.klimushenkova@ispras.ru \
    --cc=pbonzini@redhat.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).