summaryrefslogtreecommitdiffstats
path: root/replay/replay.c
diff options
context:
space:
mode:
authorAlex Bennée2017-04-05 12:05:28 +0200
committerAlex Bennée2017-04-10 11:23:38 +0200
commit982263ce714ffcc4c7c41a7b255bd29e093912fe (patch)
tree9c4b07a878d3d32e0a23a6653ef92c260cb61b90 /replay/replay.c
parentcpus: call cpu_update_icount on read (diff)
downloadqemu-982263ce714ffcc4c7c41a7b255bd29e093912fe.tar.gz
qemu-982263ce714ffcc4c7c41a7b255bd29e093912fe.tar.xz
qemu-982263ce714ffcc4c7c41a7b255bd29e093912fe.zip
replay: assert time only goes forward
If we find ourselves trying to add an event to the log where time has gone backwards it is because a vCPU event has occurred and the main-loop is not yet aware of time moving forward. This should not happen and if it does its better to fail early than generate a log that will have weird behaviour. Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Diffstat (limited to 'replay/replay.c')
-rw-r--r--replay/replay.c4
1 files changed, 4 insertions, 0 deletions
diff --git a/replay/replay.c b/replay/replay.c
index 9e0724e756..f810628cac 100644
--- a/replay/replay.c
+++ b/replay/replay.c
@@ -84,6 +84,10 @@ void replay_account_executed_instructions(void)
if (replay_state.instructions_count > 0) {
int count = (int)(replay_get_current_step()
- replay_state.current_step);
+
+ /* Time can only go forward */
+ assert(count >= 0);
+
replay_state.instructions_count -= count;
replay_state.current_step += count;
if (replay_state.instructions_count == 0) {