| /Documentation/devicetree/bindings/firmware/ |
| D | qemu,fw-cfg-mmio.yaml | 4 $id: http://devicetree.org/schemas/firmware/qemu,fw-cfg-mmio.yaml#
7 title: QEMU Firmware Configuration
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.
29 const: qemu,fw-cfg-mmio
51 compatible = "qemu,fw-cfg-mmio";
|
| /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.
13 - compatible: "qemu,pvpanic-mmio".
25 compatible = "qemu,pvpanic-mmio";
|
| D | qemu,vcpu-stall-detector.yaml | 4 $id: http://devicetree.org/schemas/misc/qemu,vcpu-stall-detector.yaml#
19 - qemu,vcpu-stall-detector
52 compatible = "qemu,vcpu-stall-detector";
|
| /Documentation/bpf/ |
| D | s390.rst | 10 document describes how to test BPF in an s390 QEMU guest.
20 * QEMU with s390 support
55 qemu-system-misc \
56 qemu-utils \
79 qemu-img create -f raw ./s390.img 1G
132 qemu-system-s390x \
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>`_
204 - `Plan 9 folder sharing over Virtio <https://wiki.qemu.org/Documentation/9psetup>`_
[all …]
|
| /Documentation/virt/kvm/x86/ |
| D | running-nested-guests.rst | 150 $ qemu-kvm -cpu host [...]
154 model supported by QEMU. e.g.::
156 $ qemu-kvm -cpu Haswell-noTSX-IBRS,vmx=on
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
[all …]
|
| D | nested-vmx.rst | 45 No modifications are required to user space (qemu). However, qemu's default
47 explicitly enabled, by giving qemu one of the following options:
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-pci-devices-pvpanic | 7 are supported by QEMU.
13 https://git.qemu.org/?p=qemu.git;a=blob_plain;f=docs/specs/pvpanic.txt
|
| 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:
17 https://qemu-project.gitlab.io/qemu/specs/fw_cfg.html
67 QEMU developers have traditionally used path name semantics
|
| D | sysfs-driver-pciback | 24 only when the guest is a stubdomain hosting device model (qemu)
|
| /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
26 www.qemu.org for more details). For cross-development,
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
|
| /Documentation/devicetree/bindings/cpufreq/ |
| D | qemu,virtual-cpufreq.yaml | 4 $id: http://devicetree.org/schemas/cpufreq/qemu,virtual-cpufreq.yaml#
21 const: qemu,virtual-cpufreq
45 compatible = "qemu,virtual-cpufreq";
|
| /Documentation/w1/masters/ |
| D | ds2490.rst | 59 - Running x86_64 2.6.24 UHCI under qemu 0.9.0 under x86_64 2.6.22-rc6
61 normally the first time the module was loaded after qemu attached
64 would fail. qemu sets a 50ms timeout and the bulk in would timeout
67 show 0 bytes written. Detaching qemu from the ds2490 hardware and
69 host did not explain the problem. My guess is a bug in either qemu
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | riscv,aplic.yaml | 30 - qemu,aplic
117 compatible = "qemu,aplic", "riscv,aplic";
131 compatible = "qemu,aplic", "riscv,aplic";
141 compatible = "qemu,aplic", "riscv,aplic";
154 compatible = "qemu,aplic", "riscv,aplic";
165 compatible = "qemu,aplic", "riscv,aplic";
|
| D | riscv,imsics.yaml | 50 - qemu,imsics
140 compatible = "qemu,imsics", "riscv,imsics";
157 compatible = "qemu,imsics", "riscv,imsics";
|
| /Documentation/dev-tools/kunit/ |
| D | run_wrapper.rst | 168 .. _kunit-on-qemu:
170 Running tests on QEMU
173 kunit_tool supports running tests on qemu as well as
174 via UML. To run tests on qemu, by default it requires two flags:
176 - ``--arch``: Selects a configs collection (Kconfig, qemu config options
183 for example: i386, x86_64, arm and so on; run on qemu.
197 This means that for most architectures, running under qemu is as simple as:
213 the ``--arch`` flag, or want to run KUnit tests on qemu using a
283 For example, i386, x86_64, arm, um, etc. Non-UML architectures run on qemu.
299 custom qemu architecture definition. This should be a python file
[all …]
|
| /Documentation/arch/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
76 qemu openrisc https://wiki.qemu.org/Documentation/Platforms/OpenRISC
|
| /Documentation/arch/s390/ |
| D | vfio-ccw.rst | 35 - The existing QEMU code which implements a simple emulated channel
38 qemu/hw/s390x/css.c
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
[all …]
|
| D | vfio-ap.rst | 509 model to QEMU, the CPU model features and facilities need to be turned on
512 /usr/bin/qemu-system-s390x ... -cpu z13,ap=on,apqci=on,apft=on,apqi=on
517 /usr/bin/qemu-system-s390x ... -cpu host,ap=off,apqci=off,apft=off,apqi=off
932 /usr/bin/qemu-system-s390x ... -cpu host,ap=on,apqci=on,apft=on,apqi=on \
937 /usr/bin/qemu-system-s390x ... -cpu host,ap=on,apqci=on,apft=on,apqi=on \
942 /usr/bin/qemu-system-s390x ... -cpu host,ap=on,apqci=on,apft=on,apqi=on \
1038 the mdev is in use by a KVM guest. If the guest is being emulated by QEMU,
1062 virsh qemu-monitor-command <guest-name> --hmp "device-del <device-id>"
1065 qemu command line with 'id=hostdev0' from the guest named 'my-guest':
1069 virsh qemu-monitor-command my-guest --hmp "device_del hostdev0"
[all …]
|
| /Documentation/admin-guide/mm/ |
| D | userfaultfd.rst | 300 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 …]
|
| /Documentation/devicetree/bindings/goldfish/ |
| D | pipe.txt | 1 Android Goldfish QEMU Pipe
|
| /Documentation/devicetree/bindings/arm/ |
| D | linux,dummy-virt.yaml | 7 title: QEMU virt machine
|
| /Documentation/driver-api/virtio/ |
| D | virtio.rst | 78 the hypervisor defines it. Taking the `QEMU virtio-console
79 <https://gitlab.com/qemu-project/qemu/-/blob/master/hw/char/virtio-console.c>`__
|
| /Documentation/filesystems/smb/ |
| D | cifsroot.rst | 97 Test it under QEMU on a kernel built with CONFIG_CIFS_ROOT and
100 # qemu-system-x86_64 -enable-kvm -cpu host -m 1024 \
|
| /Documentation/networking/device_drivers/can/ctu/ |
| D | ctucanfd-driver.rst | 31 accepted into QEMU mainline. See QEMU `CAN emulation support <https://www.qemu.org/docs/master/syst…
33 version of emulation support can be cloned from ctu-canfd branch of QEMU local
34 development `repository <https://gitlab.fel.cvut.cz/canbus/qemu-canbus>`_.
604 …CAN FD functional model for QEMU which has been integrated into QEMU mainline (`docs/system/device…
605 * Bachelor thesis Model of CAN FD Communication Controller for QEMU Emulator
|
| /Documentation/virt/kvm/ |
| D | review-checklist.rst | 23 7. Emulator changes should be accompanied by unit tests for qemu-kvm.git
|