Home
last modified time | relevance | path

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

123

/linux/Documentation/translations/zh_TW/dev-tools/
H A Dgdb-kernel-debugging.rst11 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/Documentation/translations/zh_CN/dev-tools/
H A Dgdb-kernel-debugging.rst11 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文档。
41 - 启用QEMU/KVM的gdb stub，可以通过如下方式实现
43 - 在VM启动时，通过在QEMU命令行中添加“-s”参数
47 - 在运行时通过从QEMU监视控制台发送“gdbserver”
H A Dkcsan.rst51 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-2 04/01/2014
73 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-2 04/01/2014
/linux/tools/testing/selftests/rcutorture/bin/
H A Dkvm-test-1-run.sh79 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`"
153 qemu_args="`specify_qemu_cpus "$QEMU" "$qemu_args" "$cpu_count"`"
157 qemu_args="$qemu_args `identify_qemu_args "$QEMU" "$resdir/console.log"`"
160 qemu_append="`identify_qemu_append "$QEMU"`"
202 echo $QEMU $qemu_args -m $TORTURE_QEMU_MEM -kernel $KERNEL -append \"$qemu_append $boot_args\" $TOR…
/linux/Documentation/translations/zh_CN/arch/openrisc/
H A Dopenrisc_port.rst78 QEMU是一个处理器仿真器，我们推荐它来模拟OpenRISC平台。 请按照QEMU网
79 站上的OpenRISC说明，让Linux在QEMU上运行。 你可以自己构建QEMU，但你的
/linux/Documentation/devicetree/bindings/misc/
H A 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/Documentation/process/debugging/
H A 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
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/virt/kvm/x86/
H A Drunning-nested-guests.rst154 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/drivers/misc/pvpanic/
H A DKconfig12 pvpanic is a paravirtualized device provided by QEMU; it lets
26 pvpanic is a paravirtualized device provided by QEMU which
/linux/Documentation/bpf/
H A 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/tools/testing/selftests/vsock/
H A Dvmtest.sh131 for dep in vng ${QEMU} busybox pkill ssh; do
197 qemu=$(command -v "${QEMU}")
427 QEMU="qemu-system-$(uname -m)"
434 q) QEMU=$OPTARG;;
/linux/Documentation/virt/kvm/
H A Dreview-checklist.rst55 from a guest's perspective. They run under QEMU or ``kvmtool``, and
57 that QEMU support or even on bare metal, making it possible to compare
61 Various sets of functional tests exist, such as QEMU's ``tests/functional``
71 in QEMU. If the instructions require emulation support or other code in
78 supporting them in QEMU and/or ``kvmtool``. In some cases selftests
109 as at least one of QEMU or crosvm, and guest firmware. Selftests should
/linux/Documentation/ABI/testing/
H A 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, or online at:
67 QEMU developers have traditionally used path name semantics
H A Dsysfs-bus-pci-devices-pvpanic7 are supported by QEMU.
/linux/Documentation/arch/s390/
H A 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/arch/powerpc/platforms/85xx/
H A DKconfig234 bool "QEMU generic e500 platform"
237 This option enables support for running as a QEMU guest using
238 QEMU's generic e500 machine. This is not required if you're
239 using a QEMU machine that targets a specific board, such as
243 platform works with any e500-family CPU that QEMU supports.
/linux/arch/riscv/
H A DKconfig.socs69 bool "QEMU Virt Machine"
79 This enables support for QEMU Virt Machine.
/linux/Documentation/devicetree/bindings/goldfish/
H A Dpipe.txt1 Android Goldfish QEMU Pipe
/linux/Documentation/admin-guide/mm/
H A Duserfaultfd.rst300 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/Documentation/translations/zh_CN/filesystems/
H A Dvirtiofs.rst43 请查阅 https://virtio-fs.gitlab.io/ 了解配置QEMU和virtiofsd守护程序的详细信息。
/linux/drivers/gpu/drm/virtio/
H A DKconfig12 QEMU based VMMs (like KVM or Xen).
/linux/arch/arm/boot/dts/arm/
H A 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/Documentation/translations/zh_TW/filesystems/
H A Dvirtiofs.rst44 請查閱 https://virtio-fs.gitlab.io/ 瞭解配置QEMU和virtiofsd守護程序的詳細信息。
/linux/Documentation/dev-tools/
H A Dkfence.rst107 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-2 04/01/2014
145 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-2 04/01/2014
178 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-2 04/01/2014
206 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-2 04/01/2014
233 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1 04/01/2014
/linux/tools/perf/Documentation/
H A Dperf-inject.txt98 The Process ID (PID) of the QEMU hypervisor process must be provided,
105 The QEMU option -name debug-threads=on is needed so that thread names

123