Home
last modified time | relevance | path

Searched refs:qemu (Results 1 – 25 of 52) sorted by relevance

123

/Linux-v6.1/tools/testing/selftests/rcutorture/bin/
Dkvm-test-1-run-qemu.sh20 T=${TMPDIR-/tmp}/kvm-test-1-run-qemu.sh.$$
32 echo $0: Nonexistent qemu-cmd file: $resdir/qemu-cmd
39 grep '^#' $resdir/qemu-cmd | sed -e 's/^# //' > $T/qemu-cmd-settings
40 . $T/qemu-cmd-settings
48 sed -e 's/^[^#].*$/'"$taskset_command"'& 2>\&1 \&/' < $resdir/qemu-cmd > $T/qemu-cmd
49 echo 'qemu_pid=$!' >> $T/qemu-cmd
50 echo 'echo $qemu_pid > $resdir/qemu-pid' >> $T/qemu-cmd
51 echo 'taskset -c -p $qemu_pid > $resdir/qemu-affinity' >> $T/qemu-cmd
58 ( . $T/qemu-cmd; wait `cat $resdir/qemu-pid`; echo $? > $resdir/qemu-retval ) &
66 echo Monitoring qemu job at pid $qemu_pid `date`
[all …]
Dkvm-again.sh145 …/{console.log,console.log.diags,qemu_pid,qemu-pid,qemu-retval,Warnings,kvm-test-1-run.sh.out,kvm-t…
153 for i in $rundir/*/qemu-cmd
159 …kvm-transform.sh "$kernel_dir/bzImage" "$qemu_cmd_dir/console.log" "$jitter_dir" $dur < $T/qemu-cm…
167 grep '^#' $i | sed -e 's/^# //' > $T/qemu-cmd-settings
168 . $T/qemu-cmd-settings
Dkvm-test-1-run-batch.sh35 if ! test -f "$i/qemu-cmd"
66 print "echo " scenario ": Bogus number of CPUs (old qemu-cmd?), so no taskset command.";
78 cpu_count="`grep '# TORTURE_CPU_COUNT=' $i/qemu-cmd | sed -e 's/^.*=//'`"
Dkvm-test-1-run.sh203 echo "# seconds=$seconds" >> $resdir/qemu-cmd
204 echo "# TORTURE_KCONFIG_GDB_ARG=\"$TORTURE_KCONFIG_GDB_ARG\"" >> $resdir/qemu-cmd
205 echo "# TORTURE_JITTER_START=\"$TORTURE_JITTER_START\"" >> $resdir/qemu-cmd
206 echo "# TORTURE_JITTER_STOP=\"$TORTURE_JITTER_STOP\"" >> $resdir/qemu-cmd
207 echo "# TORTURE_TRUST_MAKE=\"$TORTURE_TRUST_MAKE\"; export TORTURE_TRUST_MAKE" >> $resdir/qemu-cmd
208 echo "# TORTURE_CPU_COUNT=$cpu_count" >> $resdir/qemu-cmd
217 kvm-test-1-run-qemu.sh $resdir
Dkvm-recheck.sh45 cat $i/qemu-output
72 print_bug qemu failed
Dkvm.sh216 --qemu-args|--qemu-arg)
217 checkarg --qemu-args "(qemu arguments)" $# "$2" '^-' '^error'
221 --qemu-cmd)
222 checkarg --qemu-cmd "(qemu-system-...)" $# "$2" 'qemu-system-' '^--'
Dkvm-recheck-lock.sh28 …dur=`grep -v '^#' $i/qemu-cmd | sed -e 's/^.* locktorture.shutdown_secs=//' -e 's/ .*$//' 2> /dev/…
Dkvm-recheck-rcu.sh34 dur=`grep -v '^#' $i/qemu-cmd | sed -e 's/^.* rcutorture.shutdown_secs=//' -e 's/ .*$//'`
/Linux-v6.1/drivers/gpu/drm/tiny/
DKconfig14 tristate "DRM Support for bochs dispi vga interface (qemu stdvga)"
21 This is a KMS driver for qemu's stdvga output. Choose this option
22 for qemu.
32 This is a KMS driver for emulated cirrus device in qemu.
38 https://www.kraxel.org/blog/2014/10/qemu-using-cirrus-considered-harmful/
41 - stdvga (DRM_BOCHS, qemu -vga std, default in qemu 2.2+)
42 - qxl (DRM_QXL, qemu -vga qxl, works best with spice)
43 - virtio (DRM_VIRTIO_GPU), qemu -vga virtio)
/Linux-v6.1/Documentation/w1/masters/
Dds2490.rst59 - Running x86_64 2.6.24 UHCI under qemu 0.9.0 under x86_64 2.6.22-rc6
61 normally the first time the module was loaded after qemu attached
64 would fail. qemu sets a 50ms timeout and the bulk in would timeout
67 show 0 bytes written. Detaching qemu from the ds2490 hardware and
69 host did not explain the problem. My guess is a bug in either qemu
/Linux-v6.1/Documentation/devicetree/bindings/misc/
Dpvpanic-mmio.txt13 - compatible: "qemu,pvpanic-mmio".
25 compatible = "qemu,pvpanic-mmio";
/Linux-v6.1/Documentation/bpf/
Ds390.rst55 qemu-system-misc \
56 qemu-utils \
79 qemu-img create -f raw ./s390.img 1G
132 qemu-system-s390x \
203 - `QEMU s390x Guest Support <https://wiki.qemu.org/Documentation/Platforms/S390X>`_
204 - `Plan 9 folder sharing over Virtio <https://wiki.qemu.org/Documentation/9psetup>`_
/Linux-v6.1/Documentation/ABI/testing/
Dsysfs-bus-pci-devices-pvpanic13 https://git.qemu.org/?p=qemu.git;a=blob_plain;f=docs/specs/pvpanic.txt
Dsysfs-firmware-qemu_fw_cfg17 https://qemu-project.gitlab.io/qemu/specs/fw_cfg.html
/Linux-v6.1/Documentation/dev-tools/kunit/
Drun_wrapper.rst168 .. _kunit-on-qemu:
173 kunit_tool supports running tests on qemu as well as
174 via UML. To run tests on qemu, by default it requires two flags:
176 - ``--arch``: Selects a configs collection (Kconfig, qemu config options
183 for example: i386, x86_64, arm and so on; run on qemu.
197 This means that for most architectures, running under qemu is as simple as:
213 the ``--arch`` flag, or want to run KUnit tests on qemu using a
283 For example, i386, x86_64, arm, um, etc. Non-UML architectures run on qemu.
299 custom qemu architecture definition. This should be a python file
302 - ``--qemu_args``: Specifies additional qemu arguments, for example, ``-smp 8``.
/Linux-v6.1/Documentation/translations/zh_CN/openrisc/
Dopenrisc_port.rst83 qemu openrisc https://wiki.qemu.org/Documentation/Platforms/OpenRISC
/Linux-v6.1/Documentation/translations/zh_CN/mm/
Dhwpoison.rst45 现在主要目标是KVM客户机，但它适用于所有类型的应用程序。支持KVM需要最近的qemu-kvm
62 应用程序以温和的方式处理内存错误（例如，放弃受影响的对象） 这是KVM qemu使用的
/Linux-v6.1/tools/testing/selftests/nolibc/
DMakefile119 …$(Q)qemu-system-$(QEMU_ARCH) -display none -no-reboot -kernel "$(srctree)/$(IMAGE)" -serial stdio …
124 …$(Q)qemu-system-$(QEMU_ARCH) -display none -no-reboot -kernel "$(srctree)/$(IMAGE)" -serial stdio …
/Linux-v6.1/tools/testing/selftests/bpf/
Dvmtest.sh13 QEMU_BINARY=qemu-system-s390x
19 QEMU_BINARY=qemu-system-x86_64
234 Please install qemu or set the QEMU_BINARY environment variable.
/Linux-v6.1/tools/kvm/kvm_stat/
Dkvm_stat.service5 Before=qemu-kvm.service
/Linux-v6.1/tools/testing/selftests/wireguard/qemu/
DMakefile19 MIRROR := https://download.wireguard.com/qemu-test/distfiles/
23 default: qemu
263 TOOLCHAIN_DIR := https://download.wireguard.com/qemu-test/toolchains/20211123/
287 qemu: $(KERNEL_BZIMAGE) target
290 timeout --foreground 20m qemu-system-$(QEMU_ARCH) \
460 .PHONY: qemu build clean distclean cacheclean menuconfig
/Linux-v6.1/Documentation/openrisc/
Dopenrisc_port.rst76 qemu openrisc https://wiki.qemu.org/Documentation/Platforms/OpenRISC
/Linux-v6.1/drivers/virt/nitro_enclaves/
DKconfig25 the purpose of running unit tests (e.g. under UML or qemu). If
/Linux-v6.1/Documentation/s390/
Dvfio-ap.rst482 /usr/bin/qemu-system-s390x ... -cpu z13,ap=on,apqci=on,apft=on,apqi=on
487 /usr/bin/qemu-system-s390x ... -cpu host,ap=off,apqci=off,apft=off,apqi=off
904 /usr/bin/qemu-system-s390x ... -cpu host,ap=on,apqci=on,apft=on,apqi=on \
909 /usr/bin/qemu-system-s390x ... -cpu host,ap=on,apqci=on,apft=on,apqi=on \
914 /usr/bin/qemu-system-s390x ... -cpu host,ap=on,apqci=on,apft=on,apqi=on \
1004 virsh qemu-monitor-command <guest-name> --hmp "device-del <device-id>"
1007 qemu command line with 'id=hostdev0' from the guest named 'my-guest':
1011 virsh qemu-monitor-command my-guest --hmp "device_del hostdev0"
1013 2. A vfio_ap mediated device can be hot unplugged by attaching the qemu monitor
1014 to the guest and using the following qemu monitor command:
[all …]
/Linux-v6.1/Documentation/virt/kvm/x86/
Dnested-vmx.rst45 No modifications are required to user space (qemu). However, qemu's default
47 explicitly enabled, by giving qemu one of the following options:

123