Home
last modified time | relevance | path

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

123

/Linux-v5.15/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.15/tools/testing/selftests/rcutorture/bin/
Dkvm-test-1-run.sh78 QEMU="`identify_qemu $base_resdir/vmlinux`"
79 BOOT_IMAGE="`identify_boot_image $QEMU`"
99 QEMU="`identify_qemu vmlinux`"
100 BOOT_IMAGE="`identify_boot_image $QEMU`"
152 qemu_args="`specify_qemu_cpus "$QEMU" "$qemu_args" "$cpu_count"`"
156 qemu_args="$qemu_args `identify_qemu_args "$QEMU" "$resdir/console.log"`"
159 qemu_append="`identify_qemu_append "$QEMU"`"
201 echo $QEMU $qemu_args -m $TORTURE_QEMU_MEM -kernel $KERNEL -append \"$qemu_append $boot_args\" $TOR…
Dkvm-recheck.sh39 echo QEMU error, output:
45 echo QEMU killed
/Linux-v5.15/Documentation/translations/zh_CN/openrisc/
Dopenrisc_port.rst78 QEMU是一个处理器仿真器，我们推荐它来模拟OpenRISC平台。 请按照QEMU网
79 站上的OpenRISC说明，让Linux在QEMU上运行。 你可以自己构建QEMU，但你的
/Linux-v5.15/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.15/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
Dkfence.rst88 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-2 04/01/2014
126 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-2 04/01/2014
159 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-2 04/01/2014
187 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-2 04/01/2014
214 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1 04/01/2014
/Linux-v5.15/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.15/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.15/drivers/misc/pvpanic/
DKconfig12 pvpanic is a paravirtualized device provided by QEMU; it lets
26 pvpanic is a paravirtualized device provided by QEMU which
/Linux-v5.15/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.15/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.15/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
Dsysfs-bus-pci-devices-pvpanic7 are supported by QEMU.
/Linux-v5.15/Documentation/admin-guide/mm/
Duserfaultfd.rst189 QEMU/KVM
192 QEMU/KVM is using the ``userfaultfd`` syscall to implement postcopy live
198 migration to QEMU.
215 The QEMU in the source node writes all pages that it knows are missing
217 the QEMU running in the destination node runs ``UFFDIO_COPY|ZEROPAGE``
226 by the parallel QEMU migration thread).
228 After the QEMU postcopy thread (running in the destination node) gets
230 into the socket. The QEMU source node receives the information and
234 migration thread in the QEMU running in the destination node will
240 By the time the userfaults start, the QEMU in the destination node
[all …]
/Linux-v5.15/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.15/arch/riscv/
DKconfig.socs23 bool "QEMU Virt Machine"
32 This enables support for QEMU Virt Machine.
/Linux-v5.15/arch/powerpc/platforms/85xx/
DKconfig249 bool "QEMU generic e500 platform"
254 This option enables support for running as a QEMU guest using
255 QEMU's generic e500 machine. This is not required if you're
256 using a QEMU machine that targets a specific board, such as
260 platform works with any e500-family CPU that QEMU supports.
/Linux-v5.15/Documentation/dev-tools/kunit/
Dkunit-tool.rst151 Running Tests on QEMU
154 kunit_tool supports running tests on QEMU as well as via UML (as mentioned
155 elsewhere). The default way of running tests on QEMU requires two flags:
158 Selects a collection of configs (Kconfig as well as QEMU configs
166 e.g. i386, x86_64, arm, um, etc. Non-UML run on QEMU.
180 on QEMU using a non-default configuration. For this use case, you can write
/Linux-v5.15/Documentation/devicetree/bindings/goldfish/
Dpipe.txt1 Android Goldfish QEMU Pipe
/Linux-v5.15/drivers/gpu/drm/virtio/
DKconfig11 QEMU based VMMs (like KVM or Xen).
/Linux-v5.15/Documentation/translations/zh_CN/filesystems/
Dvirtiofs.rst43 请查阅 https://virtio-fs.gitlab.io/ 了解配置QEMU和virtiofsd守护程序的详细信息。
/Linux-v5.15/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.
/Linux-v5.15/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.15/Documentation/translations/zh_TW/filesystems/
Dvirtiofs.rst45 請查閱 https://virtio-fs.gitlab.io/ 了解配置QEMU和virtiofsd守護程序的詳細信息。

123