docs/devel/replay.rst

12 Record/replay functions are used for the deterministic replay of qemu
14 can be later used for replaying the execution anywhere and for unlimited
33 * `Deterministic Replay of System's Execution with Multi-target QEMU Simulator for Dynamic Analysis…
38  * wrappers for clock and time functions to save their return values in the log
43  * adding internal checkpoints for cpu and io synchronization
44  * network filter for recording and replaying the packets
45  * block driver for making block layer deterministic
69 the replay_mutex_lock. It used to be held only for each event being
70 written but now it is held for a whole execution period. This results
96 record/replay events used for synchronization.
110 Two functions are used for this purpose; because these actions change
132  * Real time clock. Based on host time and used only for callbacks that
133    do not change the virtual machine state. For this reason real time
143    it is used only for increasing virtual clock while virtual machine is
147 All virtual devices should use virtual clock for timers that change the guest
151 Virtual devices can also use realtime clock for the events that do not change
180 disk state. But callbacks that virtual disk controller uses for reading and
197 Sometimes the block layer uses asynchronous callbacks for its internal purposes
236 Synchronization marks (checkpoints) are used for synchronizing qemu threads
303  - EVENT_CLOCK + clock_id. Group of events for host clock read operations. Followed by:
307  - EVENT_CHECKPOINT + checkpoint_id. Checkpoint for synchronization of