Searched refs:QEMU (Results 1 – 25 of 34) sorted by relevance
12
| /Linux-v5.4/tools/testing/selftests/rcutorture/bin/ |
| D | kvm-test-1-run.sh | 76 QEMU="`identify_qemu $base_resdir/vmlinux`"
77 BOOT_IMAGE="`identify_boot_image $QEMU`"
86 QEMU="`identify_qemu vmlinux`"
87 BOOT_IMAGE="`identify_boot_image $QEMU`"
142 qemu_args="`specify_qemu_cpus "$QEMU" "$qemu_args" "$cpu_count"`"
145 qemu_args="$qemu_args `identify_qemu_args "$QEMU" "$resdir/console.log"`"
148 qemu_append="`identify_qemu_append "$QEMU"`"
161 echo "NOTE: $QEMU either did not run or was interactive" > $resdir/console.log
162 echo $QEMU $qemu_args -m $TORTURE_QEMU_MEM -kernel $KERNEL -append \"$qemu_append $boot_args\" > $r…
163 ( $QEMU $qemu_args -m $TORTURE_QEMU_MEM -kernel $KERNEL -append "$qemu_append $boot_args" > $resdir…
|
| D | kvm-recheck.sh | 35 echo QEMU error, output:
41 echo QEMU killed
|
| /Linux-v5.4/Documentation/devicetree/bindings/arm/ |
| D | fw-cfg.txt | 1 * QEMU Firmware Configuration bindings for ARM
3 QEMU's arm-softmmu and aarch64-softmmu emulation / virtualization targets
10 QEMU exposes the control and data register to ARM guests as memory mapped
12 DTB that QEMU places at the bottom of the guest's DRAM.
15 device can be found in "docs/specs/fw_cfg.txt" in the QEMU source tree.
|
| /Linux-v5.4/Documentation/devicetree/bindings/misc/ |
| 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.
|
| /Linux-v5.4/Documentation/dev-tools/ |
| 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
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
42 - Enable the gdb stub of QEMU/KVM, either
44 - at VM startup time by appending "-s" to the QEMU command line
48 - during runtime by issuing "gdbserver" from the QEMU monitor
|
| /Linux-v5.4/drivers/platform/goldfish/ |
| 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-v5.4/Documentation/openrisc/ |
| D | openrisc_port.rst | 70 QEMU is a processor emulator which we recommend for simulating the OpenRISC
71 platform. Please follow the OpenRISC instructions on the QEMU website to get
72 Linux running on QEMU. You can build QEMU yourself, but your Linux distribution
|
| /Linux-v5.4/Documentation/admin-guide/mm/ |
| D | userfaultfd.rst | 111 QEMU/KVM
114 QEMU/KVM is using the userfaultfd syscall to implement postcopy live
120 migration to QEMU.
137 The QEMU in the source node writes all pages that it knows are missing
139 the QEMU running in the destination node runs UFFDIO_COPY|ZEROPAGE
148 by the parallel QEMU migration thread).
150 After the QEMU postcopy thread (running in the destination node) gets
152 into the socket. The QEMU source node receives the information and
156 migration thread in the QEMU running in the destination node will
162 By the time the userfaults start, the QEMU in the destination node
[all …]
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| 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.
64 QEMU developers have traditionally used path name semantics
|
| /Linux-v5.4/Documentation/s390/ |
| D | vfio-ccw.rst | 35 - The existing QEMU code which implements a simple emulated channel
46 Typically, a guest virtualized via QEMU/KVM on s390 only sees
53 the functionality of passing through them to a QEMU virtual machine.
268 The use of vfio-ccw is not limited to QEMU, while QEMU is definitely a
270 bit more detail how an I/O request triggered by the QEMU guest will be
275 - Q1-Q7: QEMU side process.
298 by QEMU, issue the ccwchain to the device.
310 Signal QEMU to retrieve the result.
331 Together with the corresponding work in QEMU, we can bring the passed
|
| /Linux-v5.4/arch/powerpc/platforms/85xx/ |
| D | Kconfig | 255 bool "QEMU generic e500 platform"
260 This option enables support for running as a QEMU guest using
261 QEMU's generic e500 machine. This is not required if you're
262 using a QEMU machine that targets a specific board, such as
266 platform works with any e500-family CPU that QEMU supports.
|
| /Linux-v5.4/Documentation/devicetree/bindings/goldfish/ |
| D | pipe.txt | 1 Android Goldfish QEMU Pipe
|
| /Linux-v5.4/drivers/gpu/drm/virtio/ |
| D | Kconfig | 9 QEMU based VMMs (like KVM or Xen).
|
| /Linux-v5.4/arch/arm/boot/dts/ |
| D | arm-realview-eb.dts | 38 * To run this machine with QEMU, specify the following:
40 * Unless specified, QEMU will emulate an ARM926EJ-S core tile.
|
| D | arm-realview-eb-11mp.dts | 34 * To run this machine with QEMU, specify the following:
|
| /Linux-v5.4/drivers/gpu/drm/cirrus/ |
| D | Kconfig | 3 tristate "Cirrus driver for QEMU emulated device"
|
| /Linux-v5.4/Documentation/filesystems/ |
| D | 9p.txt | 42 For server running on QEMU host with virtio transport:
61 (from QEMU with trans_virtio module)
|
| D | virtiofs.rst | 37 Please see https://virtio-fs.gitlab.io/ for details on how to configure QEMU
|
| /Linux-v5.4/drivers/virtio/ |
| D | Kconfig | 22 virtio backends. Most QEMU based VMMs should support these devices
|
| /Linux-v5.4/Documentation/x86/x86_64/ |
| D | 5level-paging.rst | 20 QEMU 2.9 and later support 5-level paging.
|
| /Linux-v5.4/arch/alpha/ |
| D | Kconfig | 481 bool "Run under QEMU emulation"
484 Assume the presence of special features supported by QEMU PALcode
487 Generic kernels will auto-detect QEMU. But when building a
579 For emulation under QEMU, definitely say Y here, as we have other
640 when being run under QEMU.
|
| /Linux-v5.4/Documentation/filesystems/cifs/ |
| D | cifsroot.txt | 89 Test it under QEMU on a kernel built with CONFIG_CIFS_ROOT and
|
| /Linux-v5.4/drivers/firmware/ |
| D | Kconfig | 188 tristate "QEMU fw_cfg device support in sysfs"
193 Say Y or M here to enable the exporting of the QEMU firmware
199 bool "QEMU fw_cfg device parameter parsing"
|
| /Linux-v5.4/Documentation/powerpc/ |
| D | ultravisor.rst | 200 the Hypervisor/QEMU and the SVM (i.e page has mappings in SVM and
201 Hypervisor/QEMU).
315 #. QEMU attempts to access an address belonging to the SVM but the
316 page frame for that address is not mapped into QEMU's address
318 map it into QEMU's address space and issue the ``UV_PAGE_OUT``
440 #. When a shared page is unmapped from the QEMU's page table, possibly
|
| /Linux-v5.4/tools/virtio/virtio-trace/ |
| D | README | 109 the guest will stop by specification of chardev in QEMU. This blocking mode may
|
12
