| /linux/tools/testing/selftests/rcutorture/bin/ |
| H A D | kvm-test-1-run-qemu.sh | 4 # Carry out a kvm-based run for the specified qemu-cmd file, which might
7 # Usage: kvm-test-1-run-qemu.sh qemu-cmd-dir
9 # qemu-cmd-dir provides the directory containing qemu-cmd file.
14 # at the end of the qemu-cmd file are not optional.
20 T="`mktemp -d ${TMPDIR-/tmp}/kvm-test-1-run-qemu.sh.XXXXXX`"
29 if ! test -f "$resdir/qemu-cmd"
31 echo $0: Nonexistent qemu-cmd file: $resdir/qemu-cmd
37 # Obtain settings from the qemu-cmd file.
38 grep '^#' $resdir/qemu-cmd | sed -e 's/^# //' > $T/qemu-cmd-settings
39 . $T/qemu-cmd-settings
[all …]
|
| H A D | functions.sh | 144 # identify_boot_image qemu-cmd
156 qemu-system-x86_64|qemu-system-i386)
159 qemu-system-aarch64)
162 qemu-system-s390x)
174 # Returns our best guess as to which qemu command is appropriate for
183 echo qemu-system-x86_64
186 echo qemu-system-i386
189 echo qemu-system-aarch64
192 echo qemu-system-s390x
195 echo qemu-system-ppc64
[all …]
|
| H A D | kvm-test-1-run.sh | 8 # because qemu does not seem to like that much.
10 # Usage: kvm-test-1-run.sh config resdir seconds qemu-args boot_args_in
12 # qemu-args defaults to "-enable-kvm -display none -no-reboot", along
19 # Anything you specify for either qemu-args or boot_args_in is appended to
79 QEMU="`identify_qemu $base_resdir/vmlinux`"
80 BOOT_IMAGE="`identify_boot_image $QEMU`"
100 QEMU="`identify_qemu vmlinux`"
101 BOOT_IMAGE="`identify_boot_image $QEMU`"
144 # Generate -smp qemu argument.
153 qemu_args="`specify_qemu_cpus "$QEMU" "
[all...] |
| H A D | kvm-recheck.sh | 44 …if test -f "$i/qemu-retval" && test "`cat $i/qemu-retval`" -ne 0 && test "`cat $i/qemu-retval`" -n…
46 echo QEMU error, output:
47 cat $i/qemu-output
50 if test -f "$i/qemu-retval" && test "`cat $i/qemu-retval`" -eq 137
52 echo QEMU killed
92 elif test -f "$i/qemu-cmd"
94 print_bug qemu failed
|
| H A D | kvm-again.sh | 182 …/{console.log,console.log.diags,qemu_pid,qemu-pid,qemu-retval,Warnings,kvm-test-1-run.sh.out,kvm-t…
190 for i in $rundir/*/qemu-cmd
196 …kernel_dir/bzImage" "$qemu_cmd_dir/console.log" "$jitter_dir" "$dur" "$bootargs" < $T/qemu-cmd > $i
203 # Extract settings from the last qemu-cmd file transformed above.
204 grep '^#' $i | sed -e 's/^# //' > $T/qemu-cmd-settings
205 . $T/qemu-cmd-settings
|
| H A D | kvm-transform.sh | 4 # Transform a qemu-cmd file to allow reuse.
6 # Usage: kvm-transform.sh bzImage console.log jitter_dir seconds [ bootargs ] < qemu-cmd-in > qemu-…
15 # The original qemu-cmd file is provided on standard input.
16 # The transformed qemu-cmd file is on standard output.
17 # The transformation assumes that the qemu command is confined to a
|
| /linux/Documentation/devicetree/bindings/firmware/ |
| H A D | qemu,fw-cfg-mmio.yaml | 4 $id: http://devicetree.org/schemas/firmware/qemu,fw-cfg-mmio.yaml#
7 title: QEMU Firmware Configuration
13 Various QEMU emulation / virtualization targets provide the following
19 QEMU exposes the control and data register to guests as memory mapped
21 DTB that QEMU places at the bottom of the guest's DRAM.
24 device can be found in "docs/specs/fw_cfg.txt" in the QEMU source tree.
29 const: qemu,fw-cfg-mmio
51 compatible = "qemu,fw-cfg-mmio";
|
| /linux/Documentation/bpf/ |
| H A D | s390.rst | 10 document describes how to test BPF in an s390 QEMU guest.
20 * QEMU with s390 support
55 qemu-system-misc \
56 qemu-utils \
79 qemu-img create -f raw ./s390.img 1G
132 qemu-system-s390x \
173 It is possible to debug the s390 kernel using QEMU GDB stub, which is activated
174 by passing ``-s`` to QEMU.
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>`_
[all …]
|
| /linux/drivers/gpu/drm/tiny/ |
| H A D | Kconfig | 28 tristate "DRM Support for bochs dispi vga interface (qemu stdvga)"
34 This is a KMS driver for qemu's stdvga output. Choose this option
35 for qemu.
40 tristate "Cirrus driver for QEMU emulated device"
46 This is a KMS driver for emulated cirrus device in qemu.
52 https://www.kraxel.org/blog/2014/10/qemu-using-cirrus-considered-harmful/
55 - stdvga (DRM_BOCHS, qemu -vga std, default in qemu 2.2+)
56 - qxl (DRM_QXL, qemu -vga qxl, works best with spice)
57 - virtio (DRM_VIRTIO_GPU), qemu -vga virtio)
|
| /linux/Documentation/devicetree/bindings/misc/ |
| H A D | pvpanic-mmio.txt | 1 * QEMU PVPANIC MMIO Configuration bindings
3 QEMU's emulation / virtualization targets provide the following PVPANIC
9 QEMU exposes the data register to guests as memory mapped registers.
13 - compatible: "qemu,pvpanic-mmio".
25 compatible = "qemu,pvpanic-mmio";
|
| H A D | qemu,vcpu-stall-detector.yaml | 4 $id: http://devicetree.org/schemas/misc/qemu,vcpu-stall-detector.yaml#
19 - qemu,vcpu-stall-detector
52 compatible = "qemu,vcpu-stall-detector";
|
| /linux/Documentation/virt/kvm/x86/ |
| H A D | running-nested-guests.rst | 150 $ qemu-kvm -cpu host [...]
154 model supported by QEMU. e.g.::
156 $ qemu-kvm -cpu Haswell-noTSX-IBRS,vmx=on
176 feature — with QEMU, this can be done by using "host passthrough"
188 bare metal host, works as of Linux kernel 5.3 and QEMU 4.2.0 for
192 should no longer be migrated or saved (refer to QEMU documentation on
227 them running with pure emulation or what QEMU calls it as "TCG", but
229 (which could also mean, QEMU on KVM) with "nested KVM" (KVM on KVM).
236 - Kernel, libvirt, and QEMU version from L0
238 - Kernel, libvirt and QEMU version from L1
[all …]
|
| /linux/Documentation/process/debugging/ |
| H A D | gdb-kernel-debugging.rst | 6 The kernel debugger kgdb, hypervisors like QEMU or JTAG-based hardware
11 them. It focuses on QEMU/KVM virtual machines as target, but the examples can
25 - Create a virtual Linux machine for QEMU/KVM (see www.linux-kvm.org and
26 www.qemu.org for more details). For cross-development,
36 Alternatively, QEMU allows to boot the kernel directly using -kernel,
38 you do not depend on modules. See QEMU documentation for more details on
46 - Enable the gdb stub of QEMU/KVM, either
48 - at VM startup time by appending "-s" to the QEMU command line
52 - during runtime by issuing "gdbserver" from the QEMU monitor
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-firmware-qemu_fw_cfg | 5 Several different architectures supported by QEMU (x86, arm,
9 with QEMU v2.4, arbitrary fw_cfg file entries may be specified
16 in the QEMU source tree, or online at:
17 https://qemu-project.gitlab.io/qemu/specs/fw_cfg.html
67 QEMU developers have traditionally used path name semantics
|
| H A D | sysfs-bus-pci-devices-pvpanic | 7 are supported by QEMU.
13 https://git.qemu.org/?p=qemu.git;a=blob_plain;f=docs/specs/pvpanic.txt
|
| /linux/arch/powerpc/platforms/85xx/ |
| H A D | qemu_e500.c | 3 * Paravirt target for a generic QEMU e500 machine
9 * an interface contract with QEMU.
52 .name = "QEMU e500", in define_machine()
53 .compatible = "fsl,qemu-e500", in define_machine()
|
| /linux/Documentation/w1/masters/ |
| H A D | ds2490.rst | 59 - 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/Documentation/arch/s390/ |
| H A D | vfio-ccw.rst | 35 - The existing QEMU code which implements a simple emulated channel
38 qemu/hw/s390x/css.c
46 Typically, a guest virtualized via QEMU/KVM on s390 only sees
53 the functionality of passing through them to a QEMU virtual machine.
355 The use of vfio-ccw is not limited to QEMU, while QEMU is definitely a
357 bit more detail how an I/O request triggered by the QEMU guest will be
362 - Q1-Q7: QEMU side process.
385 by QEMU, issue the ccwchain to the device.
397 Signal QEMU to retrieve the result.
418 Together with the corresponding work in QEMU, we can bring the passed
[all …]
|
| H A D | vfio-ap.rst | 509 model to QEMU, the CPU model features and facilities need to be turned on
512 /usr/bin/qemu-system-s390x ... -cpu z13,ap=on,apqci=on,apft=on,apqi=on
517 /usr/bin/qemu-system-s390x ... -cpu host,ap=off,apqci=off,apft=off,apqi=off
932 /usr/bin/qemu-system-s390x ... -cpu host,ap=on,apqci=on,apft=on,apqi=on \
937 /usr/bin/qemu-system-s390x ... -cpu host,ap=on,apqci=on,apft=on,apqi=on \
942 /usr/bin/qemu-system-s390x ... -cpu host,ap=on,apqci=on,apft=on,apqi=on \
1038 the mdev is in use by a KVM guest. If the guest is being emulated by QEMU,
1062 virsh qemu-monitor-command <guest-name> --hmp "device-del <device-id>"
1065 qemu command line with 'id=hostdev0' from the guest named 'my-guest':
1069 virsh qemu-monitor-command my-guest --hmp "device_del hostdev0"
[all …]
|
| /linux/Documentation/arch/openrisc/ |
| H A D | openrisc_port.rst | 76 QEMU is a processor emulator which we recommend for simulating the OpenRISC
77 platform. Please follow the OpenRISC instructions on the QEMU website to get
78 Linux running on QEMU. You can build QEMU yourself, but your Linux distribution
82 qemu openrisc https://wiki.qemu.org/Documentation/Platforms/OpenRISC
|
| /linux/drivers/pci/controller/ |
| H A D | pci-versatile.c | 136 * For many years the kernel and QEMU were symbiotically buggy in versatile_pci_probe()
138 * QEMU therefore attempts to auto-detect old broken kernels in versatile_pci_probe()
139 * so that they still work on newer QEMU as they did on old in versatile_pci_probe()
140 * QEMU. Since we now use the correct (ie matching-hardware) in versatile_pci_probe()
142 * PCI_INTERRUPT_LINE register to tell QEMU that we expect in versatile_pci_probe()
|
| /linux/Documentation/admin-guide/mm/ |
| H A D | userfaultfd.rst | 300 QEMU/KVM
303 QEMU/KVM is using the ``userfaultfd`` syscall to implement postcopy live
309 migration to QEMU.
326 The QEMU in the source node writes all pages that it knows are missing
328 the QEMU running in the destination node runs ``UFFDIO_COPY|ZEROPAGE``
337 by the parallel QEMU migration thread).
339 After the QEMU postcopy thread (running in the destination node) gets
341 into the socket. The QEMU source node receives the information and
345 migration thread in the QEMU running in the destination node will
351 By the time the userfaults start, the QEMU in the destination node
[all …]
|
| /linux/tools/testing/selftests/nolibc/ |
| H A D | Makefile | 30 # and the Qemu program used. It is copied as-is into ARCH except for
118 # QEMU_ARCH: arch names used by qemu
151 # QEMU_ARGS : some arch-specific args to pass to qemu
230 @echo " run-user runs the executable under QEMU (uses \$$XARCH, \$$TEST)"
236 @echo " run runs the kernel in QEMU after building it (uses \$$XARCH, \$$TEST)"
237 @echo " rerun runs a previously prebuilt kernel in QEMU (uses \$$XARCH, \$$TEST)"
287 # qemu user-land test
289 $(Q)qemu-$(QEMU_ARCH_USER) ./nolibc-test > "$(CURDIR)/run.out" || :
315 …$(Q)qemu-system-$(QEMU_ARCH) -display none -no-reboot -kernel "$(IMAGE)" -initrd initramfs.cpio -s…
320 …$(Q)qemu-system-$(QEMU_ARCH) -display none -no-reboot -kernel "$(IMAGE)" -initrd initramfs.cpio -s…
|
| /linux/drivers/platform/goldfish/ |
| H A D | Kconfig | 15 tristate "Goldfish virtual device for QEMU pipes"
17 This is a virtual device to drive the QEMU pipe interface used by
|
| /linux/drivers/misc/pvpanic/ |
| H A D | Kconfig | 12 pvpanic is a paravirtualized device provided by QEMU; it lets
26 pvpanic is a paravirtualized device provided by QEMU which
|