Home
last modified time | relevance | path

Searched refs:test (Results 226 – 250 of 327) sorted by relevance

12345678910>>...14

/qemu/tests/qemu-iotests/
H A D293.out2 == creating a test image ==
5 == test that key 0 opens the image ==
/qemu/python/
H A Dsetup.cfg180 # multiple virtualenvs. This configuration file will run the test suite
183 # of python available on your system to run this test.
H A DPACKAGE.rst5 configure, and test QEMU. It is not a fully-fledged SDK and it is subject
/qemu/tests/tcg/xtensa/
H A Dtest_fp0_sqrt.S59 test sqrt_s label
H A Dmacros.inc54 .macro test name
H A Dtest_fp0_div.S55 test div_s label
H A Dtest_sr.S46 test \sr label
/qemu/docs/spin/
H A Dwin32-qemu-event.promela25 /* Basic sanity checking: test the Win32 event primitives */
H A Daio_notify_bug.promela20 * Add -DCHECK_REQ to test an alternative invariant and the
H A Daio_notify_accept.promela21 * Add -DCHECK_REQ to test an alternative invariant and the
/qemu/tests/tcg/x86_64/system/
H A Dboot.S128 test %al, %al
/qemu/tests/rocker/
H A Dbridge39 # test...
H A Dbridge-stp39 # test...
/qemu/tests/uefi-test-tools/UefiTestToolsPkg/
H A DUefiTestToolsPkg.dsc2 # edk2 platform description for the test helper UEFI applications that run in
/qemu/docs/devel/
H A Dwriting-monitor-commands.rst49 For all the examples in the next sections, the test setup is the same and is
203 Time to test our new version of the "hello-world" command. Build QEMU, run it as
248 Let's test the example above. Build QEMU, run it as defined in the "Testing"
329 To test this you have to open a user monitor and issue the "hello-world"
464 Time to test the new command. Build QEMU, run it as described in the "Testing"
533 To test this, run QEMU and type "info option-roms" in the user monitor.
H A Dblkdebug.txt21 Error injection allows test cases to trigger I/O errors at specific points.
50 -drive if=none,cache=none,file=blkdebug:blkdebug.conf:test.img,id=drive0 \
/qemu/tests/qtest/
H A Dpnv-host-i2c-test.c473 static void add_test(const char *name, void (*test)(const void *data)) in add_test()
480 qtest_add_data_func(tname, &pnv_chips[i], test); in add_test()
/qemu/docs/about/
H A Demulation.rst117 emulation. It is also useful for writing test cases and indeed a
119 to exit test code while reporting the success state.
/qemu/tcg/
H A Dtcg-ldst.c.inc44 the buffer completely. Thus we can test for overflow after
/qemu/docs/system/
H A Dmulti-process.rst48 -drive id=drive_image2,file=/build/ol7-nvme-test-1.qcow2 \
H A Dqemu-block-drivers.rst.inc604 -iscsi initiator-name=iqn.qemu.test:my-initiator
619 initiator-name = "iqn.qemu.test:my-initiator"
630 initiator-name = "iqn.qemu.test:my-initiator"
642 initiator-name = "iqn.qemu.test:my-initiator"
646 |qemu_system| -drive file=iscsi://127.0.0.1/iqn.qemu.test/1 \\
657 tgtadm --lld iscsi --op new --mode target --tid 1 -T iqn.qemu.test
664 |qemu_system| -iscsi initiator-name=iqn.qemu.test:my-initiator \\
665 -boot d -drive file=iscsi://127.0.0.1/iqn.qemu.test/1 \\
666 -cdrom iscsi://127.0.0.1/iqn.qemu.test/2
/qemu/docs/
H A DCOLO-FT.txt145 in test procedure.
159 # imagefolder="/mnt/vms/colo-test-primary"
185 # imagefolder="/mnt/vms/colo-test-secondary"
241 6. Failover test
/qemu/scripts/simplebench/
H A Dbench-backup.py50 for t in args.test:
/qemu/tests/tcg/cris/bare/
H A Dcheck_movmp.s21 ; keep the test-code but disabled, in case we need to change this again.
/qemu/.gitlab-ci.d/
H A Dcrossbuild-template.yml80 # template to their extends to save the build logs and test results

12345678910>>...14