| commit | ca9759c2a92f528f256fef0e3922416f7bb47bf9 | |
| author | Pavel Dovgalyuk <Pavel.Dovgaluk@ispras.ru> | |
| Thu, 18 Oct 2018 06:33:45 +0000 (18 09:33 +0300) | ||
| committer | Paolo Bonzini <pbonzini@redhat.com> | |
| Fri, 19 Oct 2018 11:44:12 +0000 (19 13:44 +0200) | ||
| tree | 8e1152eced839d5938854daef47eddd3c6445c6b | treesnapshot (tar.gz zip) |
| parent | a8de0115008184788525a0fab5cb74368be808a4 | commitdiff |
replay: don't process events at virtual clock checkpoint
As QEMU becomes more multi-threaded and non-synchronized, checkpoints
move from thread to thread. And the event queue that processed at checkpoints
should belong to the same thread in both record and replay executions.
This patch disables asynchronous event processing at virtual clock
checkpoint, because it may be invoked in different threads at record and
replay. This patch is temporary fix until the checkpoints are completely
refactored.
Signed-off-by: Pavel Dovgalyuk <Pavel.Dovgaluk@ispras.ru>
Message-Id: <20181018063345.7433.11678.stgit@pasha-VirtualBox>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
As QEMU becomes more multi-threaded and non-synchronized, checkpoints
move from thread to thread. And the event queue that processed at checkpoints
should belong to the same thread in both record and replay executions.
This patch disables asynchronous event processing at virtual clock
checkpoint, because it may be invoked in different threads at record and
replay. This patch is temporary fix until the checkpoints are completely
refactored.
Signed-off-by: Pavel Dovgalyuk <Pavel.Dovgaluk@ispras.ru>
Message-Id: <20181018063345.7433.11678.stgit@pasha-VirtualBox>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
| replay/replay-events.c | diffblobblamehistory | |
| replay/replay.c | diffblobblamehistory |