Home
last modified time | relevance | path

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

/linux-4.1.27/tools/testing/selftests/rcutorture/bin/
Dkvm-test-1-run.sh98 QEMU="`identify_qemu $builddir/vmlinux`"
99 BOOT_IMAGE="`identify_boot_image $QEMU`"
152 qemu_args="`specify_qemu_cpus "$QEMU" "$qemu_args" "$cpu_count"`"
155 qemu_args="$qemu_args `identify_qemu_args "$QEMU" "$builddir/console.log"`"
158 qemu_append="`identify_qemu_append "$QEMU"`"
171 echo "NOTE: $QEMU either did not run or was interactive" > $builddir/console.log
172 echo $QEMU $qemu_args -m 512 -kernel $resdir/bzImage -append \"$qemu_append $boot_args\" > $resdir/…
173 ( $QEMU $qemu_args -m 512 -kernel $resdir/bzImage -append "$qemu_append $boot_args"; echo $? > $res…
/linux-4.1.27/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 can read the corresponding data (produced by QEMU) via the data register. If
34 the QEMU source code; the structure of the data blobs corresponding to the
35 individual key values is also defined in the QEMU source code.
39 signature is "QEMU".
/linux-4.1.27/drivers/platform/goldfish/
DKconfig2 tristate "Goldfish virtual device for QEMU pipes"
4 This is a virtual device to drive the QEMU pipe interface used by
/linux-4.1.27/Documentation/
Dgdb-kernel-debugging.txt4 The kernel debugger kgdb, hypervisors like QEMU or JTAG-based hardware
9 them. It focuses on QEMU/KVM virtual machines as target, but the examples can
23 o Create a virtual Linux machine for QEMU/KVM (see www.linux-kvm.org and
34 Alternatively, QEMU allows to boot the kernel directly using -kernel,
36 you do not depend on modules. See QEMU documentation for more details on
39 o Enable the gdb stub of QEMU/KVM, either
40 - at VM startup time by appending "-s" to the QEMU command line
42 - during runtime by issuing "gdbserver" from the QEMU monitor
Dkasan.txt81 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.7.5-0-ge51488c-20140602_164612-ni…
/linux-4.1.27/arch/powerpc/platforms/85xx/
DKconfig253 bool "QEMU generic e500 platform"
256 This option enables support for running as a QEMU guest using
257 QEMU's generic e500 machine. This is not required if you're
258 using a QEMU machine that targets a specific board, such as
262 platform works with any e500-family CPU that QEMU supports.
/linux-4.1.27/drivers/gpu/drm/cirrus/
DKconfig2 tristate "Cirrus driver for QEMU emulated device"
/linux-4.1.27/drivers/virtio/
DKconfig17 virtio backends. Most QEMU based VMMs should support these devices
/linux-4.1.27/Documentation/filesystems/
D9p.txt42 For server running on QEMU host with virtio transport:
61 (from QEMU with trans_virtio module)
/linux-4.1.27/arch/alpha/
DKconfig501 bool "Run under QEMU emulation"
504 Assume the presence of special features supported by QEMU PALcode
507 Generic kernels will auto-detect QEMU. But when building a
611 For emulation under QEMU, definitely say Y here, as we have other
672 when being run under QEMU.
/linux-4.1.27/tools/virtio/virtio-trace/
DREADME109 the guest will stop by specification of chardev in QEMU. This blocking mode may
/linux-4.1.27/Documentation/devicetree/bindings/
Dvendor-prefixes.txt156 qemu QEMU, a generic and open source machine emulator and virtualizer
/linux-4.1.27/Documentation/virtual/kvm/
Dppc-pv.txt202 PAPR hypercalls are needed to run server PowerPC PAPR guests (-M pseries in QEMU).
/linux-4.1.27/drivers/net/
DKconfig260 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.
/linux-4.1.27/drivers/block/
DKconfig532 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.
/linux-4.1.27/drivers/platform/x86/
DKconfig885 a paravirtualized device provided by QEMU; it lets a virtual machine