Searched refs:QEMU (Results 1 – 25 of 63) sorted by relevance
123
| /linux-6.1.9/Documentation/devicetree/bindings/firmware/ |
| D | qemu,fw-cfg-mmio.yaml | 7 title: QEMU Firmware Configuration bindings
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.
|
| /linux-6.1.9/Documentation/translations/zh_CN/dev-tools/ |
| D | gdb-kernel-debugging.rst | 11 Kgdb内核调试器、QEMU等虚拟机管理程序或基于JTAG的硬件接口，支持在运行时使用gdb
14 此教程基于QEMU/KVM虚拟机，但文中示例也适用于其他gdb stub。
25 - 创建一个QEMU/KVM的linux虚拟机（详情请参考 www.linux-kvm.org 和 www.qemu.org ）。
33 此外，QEMU允许通过-kernel、-append、-initrd这些命令行选项直接启动内核。
34 但这通常仅在不依赖内核模块时才有效。有关此模式的更多详细信息，请参阅QEMU文档。
37 - 启用QEMU/KVM的gdb stub，可以通过如下方式实现
39 - 在VM启动时，通过在QEMU命令行中添加“-s”参数
43 - 在运行时通过从QEMU监视控制台发送“gdbserver”
|
| /linux-6.1.9/tools/testing/selftests/rcutorture/bin/ |
| D | kvm-test-1-run.sh | 78 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…
|
| D | kvm-recheck.sh | 44 echo QEMU error, output:
50 echo QEMU killed
|
| /linux-6.1.9/Documentation/translations/zh_CN/openrisc/ |
| D | openrisc_port.rst | 78 QEMU是一个处理器仿真器，我们推荐它来模拟OpenRISC平台。 请按照QEMU网
79 站上的OpenRISC说明，让Linux在QEMU上运行。 你可以自己构建QEMU，但你的
|
| /linux-6.1.9/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-6.1.9/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-6.1.9/Documentation/virt/kvm/x86/ |
| D | running-nested-guests.rst | 154 model supported by QEMU. e.g.::
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
240 - QEMU command-line of L1 -- when using libvirt, you'll find it here:
243 - QEMU command-line of L2 -- as above, when using libvirt, get the
[all …]
|
| /linux-6.1.9/drivers/platform/goldfish/ |
| D | Kconfig | 14 tristate "Goldfish virtual device for QEMU pipes"
16 This is a virtual device to drive the QEMU pipe interface used by
|
| /linux-6.1.9/drivers/misc/pvpanic/ |
| D | Kconfig | 12 pvpanic is a paravirtualized device provided by QEMU; it lets
26 pvpanic is a paravirtualized device provided by QEMU which
|
| /linux-6.1.9/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-6.1.9/Documentation/bpf/ |
| D | s390.rst | 10 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-6.1.9/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, or online at:
67 QEMU developers have traditionally used path name semantics
|
| D | sysfs-bus-pci-devices-pvpanic | 7 are supported by QEMU.
|
| /linux-6.1.9/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.
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-6.1.9/arch/powerpc/platforms/85xx/ |
| D | Kconfig | 242 bool "QEMU generic e500 platform"
245 This option enables support for running as a QEMU guest using
246 QEMU's generic e500 machine. This is not required if you're
247 using a QEMU machine that targets a specific board, such as
251 platform works with any e500-family CPU that QEMU supports.
|
| /linux-6.1.9/Documentation/admin-guide/mm/ |
| D | userfaultfd.rst | 224 QEMU/KVM
227 QEMU/KVM is using the ``userfaultfd`` syscall to implement postcopy live
233 migration to QEMU.
250 The QEMU in the source node writes all pages that it knows are missing
252 the QEMU running in the destination node runs ``UFFDIO_COPY|ZEROPAGE``
261 by the parallel QEMU migration thread).
263 After the QEMU postcopy thread (running in the destination node) gets
265 into the socket. The QEMU source node receives the information and
269 migration thread in the QEMU running in the destination node will
275 By the time the userfaults start, the QEMU in the destination node
[all …]
|
| /linux-6.1.9/arch/riscv/ |
| D | Kconfig.socs | 30 bool "QEMU Virt Machine"
42 This enables support for QEMU Virt Machine.
|
| /linux-6.1.9/Documentation/devicetree/bindings/goldfish/ |
| D | pipe.txt | 1 Android Goldfish QEMU Pipe
|
| /linux-6.1.9/Documentation/devicetree/bindings/arm/ |
| D | linux,dummy-virt.yaml | 7 title: QEMU virt machine
|
| /linux-6.1.9/drivers/gpu/drm/virtio/ |
| D | Kconfig | 11 QEMU based VMMs (like KVM or Xen).
|
| /linux-6.1.9/Documentation/translations/zh_CN/filesystems/ |
| D | virtiofs.rst | 43 请查阅 https://virtio-fs.gitlab.io/ 了解配置QEMU和virtiofsd守护程序的详细信息。
|
| /linux-6.1.9/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.
|
| /linux-6.1.9/Documentation/userspace-api/ |
| D | iommu.rst | 90 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-6.1.9/Documentation/translations/zh_TW/filesystems/ |
| D | virtiofs.rst | 45 請查閱 https://virtio-fs.gitlab.io/ 了解配置QEMU和virtiofsd守護程序的詳細信息。
|
123