Home
last modified time | relevance | path

Searched refs:QEMU (Results 1 – 25 of 44) sorted by relevance

12

/Linux-v5.10/tools/testing/selftests/rcutorture/bin/
Dkvm-test-1-run.sh79 QEMU="`identify_qemu $base_resdir/vmlinux`"
80 BOOT_IMAGE="`identify_boot_image $QEMU`"
89 QEMU="`identify_qemu vmlinux`"
90 BOOT_IMAGE="`identify_boot_image $QEMU`"
143 qemu_args="`specify_qemu_cpus "$QEMU" "$qemu_args" "$cpu_count"`"
147 qemu_args="$qemu_args `identify_qemu_args "$QEMU" "$resdir/console.log"`"
150 qemu_append="`identify_qemu_append "$QEMU"`"
160 echo $QEMU $qemu_args -m $TORTURE_QEMU_MEM -kernel $KERNEL -append \"$qemu_append $boot_args\" $TOR…
174 echo "NOTE: $QEMU either did not run or was interactive" > $resdir/console.log
Dkvm-recheck.sh39 echo QEMU error, output:
45 echo QEMU killed
/Linux-v5.10/Documentation/devicetree/bindings/arm/
Dfw-cfg.txt1 * 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.10/Documentation/devicetree/bindings/misc/
Dpvpanic-mmio.txt1 * 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.10/Documentation/dev-tools/
Dgdb-kernel-debugging.rst6 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.10/Documentation/virt/kvm/
Drunning-nested-guests.rst152 model supported by QEMU. e.g.::
174 feature — with QEMU, this can be done by using "host passthrough"
186 bare metal host, works as of Linux kernel 5.3 and QEMU 4.2.0 for
190 should no longer be migrated or saved (refer to QEMU documentation on
225 them running with pure emulation or what QEMU calls it as "TCG", but
227 (which could also mean, QEMU on KVM) with "nested KVM" (KVM on KVM).
234 - Kernel, libvirt, and QEMU version from L0
236 - Kernel, libvirt and QEMU version from L1
238 - QEMU command-line of L1 -- when using libvirt, you'll find it here:
241 - QEMU command-line of L2 -- as above, when using libvirt, get the
[all …]
/Linux-v5.10/drivers/platform/goldfish/
DKconfig14 tristate "Goldfish virtual device for QEMU pipes"
16 This is a virtual device to drive the QEMU pipe interface used by
/Linux-v5.10/Documentation/openrisc/
Dopenrisc_port.rst70 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.10/Documentation/bpf/
Ds390.rst10 document describes how to test BPF in an s390 QEMU guest.
20 * QEMU with s390 support
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>`_
205 - `Using GDB with QEMU <https://wiki.osdev.org/Kernel_Debugging#Use_GDB_with_QEMU>`_
/Linux-v5.10/arch/riscv/
DKconfig.socs14 bool "QEMU Virt Machine"
23 This enables support for QEMU Virt Machine.
/Linux-v5.10/Documentation/ABI/testing/
Dsysfs-firmware-qemu_fw_cfg5 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.
66 QEMU developers have traditionally used path name semantics
/Linux-v5.10/Documentation/admin-guide/mm/
Duserfaultfd.rst163 QEMU/KVM
166 QEMU/KVM is using the ``userfaultfd`` syscall to implement postcopy live
172 migration to QEMU.
189 The QEMU in the source node writes all pages that it knows are missing
191 the QEMU running in the destination node runs ``UFFDIO_COPY|ZEROPAGE``
200 by the parallel QEMU migration thread).
202 After the QEMU postcopy thread (running in the destination node) gets
204 into the socket. The QEMU source node receives the information and
208 migration thread in the QEMU running in the destination node will
214 By the time the userfaults start, the QEMU in the destination node
[all …]
/Linux-v5.10/Documentation/s390/
Dvfio-ccw.rst35 - 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.
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
430 in QEMU's s390-ccw bios as of QEMU 4.1.
/Linux-v5.10/arch/powerpc/platforms/85xx/
DKconfig255 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.10/Documentation/devicetree/bindings/goldfish/
Dpipe.txt1 Android Goldfish QEMU Pipe
/Linux-v5.10/drivers/gpu/drm/virtio/
DKconfig10 QEMU based VMMs (like KVM or Xen).
/Linux-v5.10/Documentation/translations/zh_CN/filesystems/
Dvirtiofs.rst43 请查阅 https://virtio-fs.gitlab.io/ 了解配置QEMU和virtiofsd守护程序的详细信息。
/Linux-v5.10/arch/arm/boot/dts/
Darm-realview-eb.dts38 * To run this machine with QEMU, specify the following:
40 * Unless specified, QEMU will emulate an ARM926EJ-S core tile.
Darm-realview-eb-11mp.dts34 * To run this machine with QEMU, specify the following:
/Linux-v5.10/Documentation/userspace-api/
Diommu.rst90 User applications such as QEMU are expected to import kernel UAPI
92 For example, an older QEMU (with older kernel header) can run on newer
93 kernel. Newer QEMU (with new kernel header) may refuse to initialize
107 Take VFIO as example, upon request from VFIO userspace (e.g. QEMU),
/Linux-v5.10/drivers/vfio/pci/
DKconfig55 configuration for zPCI devices. This enables userspace (e.g. QEMU)
/Linux-v5.10/Documentation/filesystems/
D9p.rst47 For server running on QEMU host with virtio transport::
69 (from QEMU with trans_virtio module)
/Linux-v5.10/Documentation/x86/x86_64/
D5level-paging.rst20 QEMU 2.9 and later support 5-level paging.
/Linux-v5.10/drivers/firmware/
DKconfig188 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.10/arch/alpha/
DKconfig483 bool "Run under QEMU emulation"
486 Assume the presence of special features supported by QEMU PALcode
489 Generic kernels will auto-detect QEMU. But when building a
581 For emulation under QEMU, definitely say Y here, as we have other
642 when being run under QEMU.

12