Searched full:qemu (Results 1 – 25 of 373) sorted by relevance
12345678910>>...15
| /kernel/linux/linux-6.6/tools/testing/selftests/rcutorture/bin/ |
| D | kvm-test-1-run-qemu.sh | 4 # Carry out a kvm-based run for the specified qemu-cmd file, which might
7 # Usage: kvm-test-1-run-qemu.sh qemu-cmd-dir
9 # qemu-cmd-dir provides the directory containing qemu-cmd file.
14 # at the end of the qemu-cmd file are not optional.
20 T="`mktemp -d ${TMPDIR-/tmp}/kvm-test-1-run-qemu.sh.XXXXXX`"
29 if ! test -f "$resdir/qemu-cmd"
31 echo $0: Nonexistent qemu-cmd file: $resdir/qemu-cmd
37 # Obtain settings from the qemu-cmd file.
38 grep '^#' $resdir/qemu-cmd | sed -e 's/^# //' > $T/qemu-cmd-settings
39 . $T/qemu-cmd-settings
[all …]
|
| D | functions.sh | 144 # identify_boot_image qemu-cmd
156 qemu-system-x86_64|qemu-system-i386)
159 qemu-system-aarch64)
162 qemu-system-s390x)
174 # Returns our best guess as to which qemu command is appropriate for
183 echo qemu-system-x86_64
186 echo qemu-system-i386
189 echo qemu-system-aarch64
192 echo qemu-system-s390x
195 echo qemu-system-ppc64
[all …]
|
| D | kvm-test-1-run.sh | 8 # because qemu does not seem to like that much.
10 # Usage: kvm-test-1-run.sh config resdir seconds qemu-args boot_args_in
12 # qemu-args defaults to "-enable-kvm -display none -no-reboot", along
19 # Anything you specify for either qemu-args or boot_args_in is appended to
77 QEMU="`identify_qemu $base_resdir/vmlinux`"
78 BOOT_IMAGE="`identify_boot_image $QEMU`"
98 QEMU="`identify_qemu vmlinux`"
99 BOOT_IMAGE="`identify_boot_image $QEMU`"
142 # Generate -smp qemu argument.
151 qemu_args="`specify_qemu_cpus "$QEMU" "$qemu_args" "$cpu_count"`"
[all …]
|
| D | kvm-test-1-run-batch.sh | 10 # containing a ready-to-run qemu-cmd file.
34 if ! test -f "$i/qemu-cmd"
36 echo Scenario lacks a command file: \"$i/qemu-cmd\" 1>&2
44 # Extract settings from the qemu-cmd file.
45 grep '^#' $1/qemu-cmd | sed -e 's/^# //' > $T/qemu-cmd-settings
46 . $T/qemu-cmd-settings
55 echo ---- System running test: `uname -a` > $i/kvm-test-1-run-qemu.sh.out
56 echo > $i/kvm-test-1-run-qemu.sh.out
65 print "echo " scenario ": Bogus number of CPUs (old qemu-cmd?), so no taskset command.";
77 cpu_count="`grep '# TORTURE_CPU_COUNT=' $i/qemu-cmd | sed -e 's/^.*=//'`"
[all …]
|
| D | kvm-recheck.sh | 44 …if test -f "$i/qemu-retval" && test "`cat $i/qemu-retval`" -ne 0 && test "`cat $i/qemu-retval`" -n…
46 echo QEMU error, output:
47 cat $i/qemu-output
50 if test -f "$i/qemu-retval" && test "`cat $i/qemu-retval`" -eq 137
52 echo QEMU killed
92 elif test -f "$i/qemu-cmd"
94 print_bug qemu failed
|
| D | kvm-again.sh | 182 …/{console.log,console.log.diags,qemu_pid,qemu-pid,qemu-retval,Warnings,kvm-test-1-run.sh.out,kvm-t…
190 for i in $rundir/*/qemu-cmd
196 …kernel_dir/bzImage" "$qemu_cmd_dir/console.log" "$jitter_dir" "$dur" "$bootargs" < $T/qemu-cmd > $i
203 # Extract settings from the last qemu-cmd file transformed above.
204 grep '^#' $i | sed -e 's/^# //' > $T/qemu-cmd-settings
205 . $T/qemu-cmd-settings
|
| D | kvm-transform.sh | 4 # Transform a qemu-cmd file to allow reuse.
6 # Usage: kvm-transform.sh bzImage console.log jitter_dir seconds [ bootargs ] < qemu-cmd-in > qemu-…
15 # The original qemu-cmd file is provided on standard input.
16 # The transformed qemu-cmd file is on standard output.
17 # The transformation assumes that the qemu command is confined to a
|
| /kernel/linux/linux-5.10/tools/testing/selftests/rcutorture/bin/ |
| D | functions.sh | 111 # identify_boot_image qemu-cmd
123 qemu-system-x86_64|qemu-system-i386)
126 qemu-system-aarch64)
138 # Returns our best guess as to which qemu command is appropriate for
147 echo qemu-system-x86_64
150 echo qemu-system-i386
153 echo qemu-system-aarch64
156 echo qemu-system-ppc64
158 echo Cannot figure out what qemu command to use! 1>&2
160 # Usually this will be one of /usr/bin/qemu-system-*
[all …]
|
| D | kvm-test-1-run.sh | 8 # because qemu does not seem to like that much.
10 # Usage: kvm-test-1-run.sh config builddir resdir seconds qemu-args boot_args
12 # qemu-args defaults to "-enable-kvm -nographic", along with arguments
18 # Anything you specify for either qemu-args or boot_args is appended to
79 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`"
134 # Generate -smp qemu argument.
143 qemu_args="`specify_qemu_cpus "$QEMU" "$qemu_args" "$cpu_count"`"
[all …]
|
| D | kvm-recheck.sh | 37 …if test -f "$i/qemu-retval" && test "`cat $i/qemu-retval`" -ne 0 && test "`cat $i/qemu-retval`" -n…
39 echo QEMU error, output:
40 cat $i/qemu-output
43 if test -f "$i/qemu-retval" && test "`cat $i/qemu-retval`" -eq 137
45 echo QEMU killed
65 elif test -f "$i/qemu-cmd"
67 print_bug qemu failed
|
| D | kvm-transform.sh | 4 # Transform a qemu-cmd file to allow reuse.
6 # Usage: kvm-transform.sh bzImage console.log < qemu-cmd-in > qemu-cmd-out
11 # The original qemu-cmd file is provided on standard input.
12 # The transformed qemu-cmd file is on standard output.
13 # The transformation assumes that the qemu command is confined to a
|
| /kernel/linux/linux-6.6/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";
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/arm/ |
| D | fw-cfg.txt | 1 * 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.
20 - compatible: "qemu,fw-cfg-mmio".
35 compatible = "qemu,fw-cfg-mmio";
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-6.6/drivers/gpu/drm/tiny/ |
| D | Kconfig | 14 tristate "DRM Support for bochs dispi vga interface (qemu stdvga)"
21 This is a KMS driver for qemu's stdvga output. Choose this option
22 for qemu.
27 tristate "Cirrus driver for QEMU emulated device"
32 This is a KMS driver for emulated cirrus device in qemu.
38 https://www.kraxel.org/blog/2014/10/qemu-using-cirrus-considered-harmful/
41 - stdvga (DRM_BOCHS, qemu -vga std, default in qemu 2.2+)
42 - qxl (DRM_QXL, qemu -vga qxl, works best with spice)
43 - virtio (DRM_VIRTIO_GPU), qemu -vga virtio)
|
| /kernel/linux/linux-5.10/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";
|
| /kernel/linux/linux-6.6/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";
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/tiny/ |
| D | Kconfig | 4 tristate "Cirrus driver for QEMU emulated device"
9 This is a KMS driver for emulated cirrus device in qemu.
15 https://www.kraxel.org/blog/2014/10/qemu-using-cirrus-considered-harmful/
18 - stdvga (DRM_BOCHS, qemu -vga std, default in qemu 2.2+)
19 - qxl (DRM_QXL, qemu -vga qxl, works best with spice)
20 - virtio (DRM_VIRTIO_GPU), qemu -vga virtio)
|
| /kernel/linux/linux-5.10/Documentation/virt/kvm/ |
| D | running-nested-guests.rst | 148 $ qemu-kvm -cpu host [...]
152 model supported by QEMU. e.g.::
154 $ qemu-kvm -cpu Haswell-noTSX-IBRS,vmx=on
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
[all …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-6.6/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:
17 https://qemu-project.gitlab.io/qemu/specs/fw_cfg.html
67 QEMU developers have traditionally used path name semantics
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/mm/ |
| D | userfaultfd.rst | 163 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 …]
|
12345678910>>...15