Home
last modified time | relevance | path

Searched refs:steps (Results 1 – 25 of 38) sorted by relevance

12

/qemu/tests/functional/
H A Dreverse_debugging.py144 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])
192 self.check_pc(g, steps[-1])
193 logger.info('successfully reached %x' % steps[-1])
/qemu/tests/qtest/
H A Dnpcm7xx_watchdog_timer-test.c262 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()
/qemu/docs/system/arm/
H A Dimx8mp-evk.rst38 of writing and involves two steps. First run the following commands in the
/qemu/docs/system/
H A Dsriov.rst34 You may also need to perform additional steps to activate the SR-IOV feature on
H A Dreplay.rst199 commands. The first one steps single instruction backwards in time,
215 between the snapshots. Each of the passes include the following steps:
/qemu/
H A DREADME.rst50 of other UNIX targets. The simple steps to build QEMU are:
102 automate everything, so you may want to go through the above steps
/qemu/target/ppc/
H A Dpower8-pmu-regs.c.inc212 /* 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/system/devices/
H A Digb.rst35 However, you may also need to perform additional steps to activate SR-IOV
/qemu/docs/system/loongarch/
H A Dvirt.rst37 can be accessed by following steps.
/qemu/docs/devel/migration/
H A Ddirty-limit.rst30 launched, executes the loop, which consists of three steps:
/qemu/docs/devel/testing/
H A Dacpi-bits.rst86 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 Dmain.rst445 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.
H A Dqgraph.rst76 Execution steps
79 The basic framework steps are the following:
/qemu/docs/devel/
H A Dconflict-resolution.rst36 seek further information, or will make a determination on next steps.
H A Ds390-dasd-ipl.rst7 The s390 hardware IPL process consists of the following steps.
H A Dwriting-monitor-commands.rst26 Generally speaking, the following steps should be taken in order to write a
42 The following sections will demonstrate each of the steps above. We will start
H A Dtcg.rst72 following steps:
/qemu/docs/specs/
H A Dspdm.rst27 To use SPDM-Utils you will need to do the following steps. Details are included
H A Dacpi_cpu_hotplug.rst198 Use following steps to detect and enable modern CPU hotplug interface:
/qemu/docs/
H A Dmulti-thread-compression.txt140 So, only the first two steps are required to use the multiple
/qemu/docs/system/ppc/
H A Dppce500.rst110 in 32-bit mode, use the same 64-bit configuration steps except the defconfig
/qemu/qapi/
H A Djob.json66 # @pending: The job has finished its work, but has finalization steps
/qemu/hw/virtio/
H A Dvirtio.c941 unsigned int i, steps, max_steps; in virtqueue_ordered_fill() local
944 steps = 0; in virtqueue_ordered_fill()
952 while (steps <= max_steps) { in virtqueue_ordered_fill()
961 steps += vq->used_elems[i].ndescs; in virtqueue_ordered_fill()
972 if (steps >= max_steps) { in virtqueue_ordered_fill()
/qemu/docs/system/riscv/
H A Dvirt.rst236 A TPM device can be connected to the virt board by following the steps below.
/qemu/target/hexagon/idef-parser/
H A DREADME.rst108 on its' input. There are two preprocessing steps applied to the generated
450 Implementing an instruction goes through several sequential steps, here are some

12