| /qemu/tests/functional/ |
| H A D | reverse_debugging.py | 32 STEPS = 10 variable in ReverseDebugging
121 while self.vm_get_icount(vm) <= self.STEPS:
126 logger.info("recorded log with %s+ steps" % last_icount)
144 steps = []
146 for _ in range(self.STEPS):
149 steps.append(pc)
154 for addr in steps[::-1]:
161 for addr in steps:
168 for addr in steps:
186 logger.info('running reverse continue to reach %x' % steps[-1])
[all …]
|
| /qemu/tests/qtest/ |
| H A D | npcm7xx_watchdog_timer-test.c | 262 int64_t remaining_steps, steps; in test_pause() local
271 steps = remaining_steps / 2; in test_pause()
272 remaining_steps -= steps; in test_pause()
273 qtest_clock_step(qts, steps); in test_pause()
280 qtest_clock_step(qts, steps << 4); in test_pause()
|
| H A D | lsm303dlhc-mag-test.c | 82 /* Should return 23.5 C due to 0.125°C steps. */ in send_and_receive()
|
| /qemu/.github/workflows/ |
| H A D | lockdown.yml | 15 steps:
|
| /qemu/ |
| H A D | README.rst | 50 of other UNIX targets. The simple steps to build QEMU are:
102 automate everything, so you may want to go through the above steps
|
| H A D | .travis.yml | 46 # Common first phase for all steps
|
| /qemu/include/hw/virtio/ |
| H A D | vhost-user-blk.h | 44 * There are at least two steps of initialization of the
|
| H A D | vhost-user.h | 105 * do all the steps and handle potential races due to VM shutdowns.
|
| /qemu/docs/system/arm/ |
| H A D | imx8mp-evk.rst | 38 of writing and involves two steps. First run the following commands in the
|
| /qemu/target/ppc/ |
| H A D | power8-pmu-regs.c.inc | 212 /* The remaining steps are similar to PMCs 1-4 userspace read */
245 /* The remaining steps are similar to PMCs 1-4 userspace write */
|
| /qemu/docs/devel/testing/ |
| H A D | acpi-bits.rst | 86 In order to run this test, please perform the following steps from the QEMU
131 Then make your additions and changes here. Therefore, the steps are:
|
| H A D | qtest.rst | 37 Steps to add a new QTest case are:
|
| H A D | main.rst | 445 container build steps over and over again. This can be overridden
492 the following steps are needed:
500 If that is the case, some extra preparation steps will be required
600 below steps to debug it:
655 It is possible to build and test with TSan, with a few additional steps.
656 These steps are normally done automatically in the docker.
|
| /qemu/docs/system/ |
| H A D | sriov.rst | 34 You may also need to perform additional steps to activate the SR-IOV feature on
|
| H A D | replay.rst | 199 commands. The first one steps single instruction backwards in time,
215 between the snapshots. Each of the passes include the following steps:
|
| /qemu/hw/net/ |
| H A D | npcm_gmac.c | 315 * Comments have steps that relate to the in gmac_receive()
316 * receiving process steps in pg 386 in gmac_receive()
511 * Comments about steps refer to steps for in gmac_try_send_next_packet()
524 /* steps 1&2 */ in gmac_try_send_next_packet()
|
| /qemu/.gitlab/issue_templates/ |
| H A D | bug.md | 47 ## Steps to reproduce
|
| /qemu/docs/system/devices/ |
| H A D | igb.rst | 35 However, you may also need to perform additional steps to activate SR-IOV
|
| /qemu/docs/devel/ |
| H A D | conflict-resolution.rst | 36 seek further information, or will make a determination on next steps.
|
| H A D | s390-dasd-ipl.rst | 7 The s390 hardware IPL process consists of the following steps.
|
| /qemu/docs/system/loongarch/ |
| H A D | virt.rst | 37 can be accessed by following steps.
|
| /qemu/docs/devel/migration/ |
| H A D | dirty-limit.rst | 30 launched, executes the loop, which consists of three steps:
|
| /qemu/docs/specs/ |
| H A D | spdm.rst | 27 To use SPDM-Utils you will need to do the following steps. Details are included
|
| /qemu/docs/ |
| H A D | COLO-FT.txt | 237 5. After the above steps, you will see, whenever you make changes to PVM, SVM will be synced.
283 Start the new Secondary (Steps 2 and 3 above), then on the Primary:
311 Start the new Secondary (Steps 2 and 3 above, but with primary_ip=127.0.0.2),
|
| /qemu/docs/system/ppc/ |
| H A D | ppce500.rst | 110 in 32-bit mode, use the same 64-bit configuration steps except the defconfig
|