Searched refs:deterministic (Results 1 – 14 of 14) sorted by relevance
| /qemu/util/ |
| A D | guest-random.c | 21 static bool deterministic; variable
52 if (unlikely(deterministic)) { in qemu_guest_getrandom()
72 if (deterministic) { in qemu_guest_random_seed_thread_part1()
83 if (deterministic) { in qemu_guest_random_seed_thread_part2()
97 deterministic = true; in qemu_guest_random_seed_main()
|
| /qemu/docs/devel/ |
| A D | replay.rst | 12 Record/replay functions are used for the deterministic replay of qemu
13 execution. Execution recording writes a non-deterministic events log, which
16 non-deterministic events including external input, hardware clocks,
26 All non-deterministic events are coming from these devices. But to
45 * block driver for making block layer deterministic
71 in a deterministic ping-pong between the two main threads.
134 clock and timers does not affect deterministic replay at all.
141 make the execution deterministic.
148 state. Virtual clock is deterministic, therefore such timers are deterministic
178 Disk I/O events are completely deterministic in our model, because
[all …]
|
| A D | tcg-icount.rst | 21 deterministic execution and is an essential part of the record/replay
|
| A D | lockcnt.rst | 71 With reference counting, reclamation is deterministic.
|
| A D | reset.rst | 43 have some non-deterministic state they want to reinitialize to a different
|
| /qemu/docs/system/ |
| A D | replay.rst | 13 Record/replay functions are used for the deterministic replay of qemu execution.
14 Execution recording writes a non-deterministic events log, which can be later
17 Execution replaying reads the log and replays all non-deterministic events
29 * Performs deterministic replay of all operations with keyboard and mouse
72 Record/replay system is based on saving and replaying non-deterministic
73 events (e.g. keyboard input) and simulating deterministic ones (e.g. reading
74 from HDD or memory of the VM). Saving only non-deterministic events makes
77 The following non-deterministic data from peripheral devices is saved into
79 serial port input, and hardware clocks (they are non-deterministic
82 instructions are not saved into the log, because they are deterministic and
[all …]
|
| /qemu/qapi/ |
| A D | replay.json | 18 # @record: record mode. All non-deterministic data is written into
21 # @play: replay mode. Non-deterministic data required for system
|
| /qemu/docs/devel/testing/ |
| A D | blkdebug.rst | 170 deterministic ordering when multiple requests are in flight.
|
| /qemu/docs/system/arm/ |
| A D | virt.rst | 181 DTB to be non-deterministic. It would be the responsibility of
|
| /qemu/docs/ |
| A D | rdma.txt | 28 RDMA helps make your migration more deterministic under heavy load because
|
| /qemu/docs/devel/migration/ |
| A D | main.rst | 471 in a ``post_load`` hook.) Otherwise, restore will not be deterministic,
|
| /qemu/docs/about/ |
| A D | emulation.rst | 816 When running system emulation you can also enable deterministic
|
| /qemu/ |
| A D | qemu-options.hx | 4670 Force the guest to use a deterministic pseudo-random number
4834 Note that while this option can give deterministic behavior, it does
4845 deterministic execution times from the guest point of view.
4862 When the ``rr`` option is specified deterministic record/replay is
|
| /qemu/docs/interop/ |
| A D | vhost-user.rst | 1880 The reply payload gives QEMU a deterministic indication of the result
|
Completed in 43 milliseconds