| /OK3568_Linux_fs/yocto/poky/documentation/dev-manual/ |
| H A D | qemu.rst | 4 Using the Quick EMUlator (QEMU)
7 The Yocto Project uses an implementation of the Quick EMUlator (QEMU)
10 EMUlator (QEMU) and other QEMU information helpful for development
16 Within the context of the Yocto Project, QEMU is an emulator and
19 QEMU is useful for running and testing images and applications on
21 Among other things, the Yocto Project uses QEMU to run automated Quality
26 This implementation is not the same as QEMU in general.
29 implementation of QEMU.
31 For official information and documentation on QEMU in general, see the
34 - `QEMU Website <https://wiki.qemu.org/Main_Page>`__\ *:* The official
[all …]
|
| /OK3568_Linux_fs/buildroot/board/qemu/arm-vexpress-tz/ |
| H A D | readme.txt | 1 Board qemu_arm_vexpress_tz builds a QEMU ARMv7-A target system with
4 builds of the QEMU host ARM target emulator.
9 The BIOS used in the QEMU host is the ARM Trusted Firmware-A (TF-A).
10 In our configuration, U-Boot uses QEMU semihosting file access to load the
23 in the terminal that started QEMU.
34 TF-A is used as QEMU BIOS. Its BL1 image boots and load its BL2 image. In turn,
38 QEMU natively hosts and loads in RAM the QEMU ARM target device tree. OP-TEE
50 The ARM Trusted Firmware outputs its traces on the QEMU standard (first)
53 The OP-TEE OS uses the QEMU second serial interface.
56 -serial stdio in the QEMU command line. I.e, the following enables 2 serial
[all …]
|
| /OK3568_Linux_fs/buildroot/package/qemu/ |
| H A D | Config.in | 8 comment "QEMU requires a toolchain with wchar, threads, gcc >= 8"
15 bool "QEMU"
25 QEMU is a generic and open source machine emulator and
28 When used as a machine emulator, QEMU can run OSes and
33 When used as a virtualizer, QEMU achieves near native
35 host CPU. QEMU supports virtualization when executing under
37 Linux. When using KVM, QEMU can virtualize x86, server and
49 Enter here the list of QEMU targets you want to build. For
78 full TCP/IP stack within QEMU and uses that stack to implement
93 Say 'y' to build all system emulators/virtualisers that QEMU
[all …]
|
| /OK3568_Linux_fs/u-boot/board/emulation/ |
| H A D | Kconfig | 13 bool "QEMU x86"
15 This is the QEMU emulated x86 board. U-Boot supports running
17 There are two types of x86 boards supported by QEMU which are
18 supported by U-Boot. They are via QEMU '-M pc', an i440FX/PIIX
22 bool "QEMU x86 64-bit"
24 This is the QEMU emulated x86 64-bit board. With this config
|
| /OK3568_Linux_fs/kernel/tools/testing/selftests/rcutorture/bin/ |
| H A D | kvm-test-1-run.sh | 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`"
143 qemu_args="`specify_qemu_cpus "$QEMU" "$qemu_args" "$cpu_count"`"
147 qemu_args="$qemu_args `identify_qemu_args "$QEMU" "$resdir/console.log"`"
150 qemu_append="`identify_qemu_append "$QEMU"`"
160 echo $QEMU $qemu_args -m $TORTURE_QEMU_MEM -kernel $KERNEL -append \"$qemu_append $boot_args\" $TOR…
174 echo "NOTE: $QEMU either did not run or was interactive" > $resdir/console.log
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/arm/ |
| H A 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.
|
| /OK3568_Linux_fs/u-boot/doc/ |
| H A D | README.boston | 14 QEMU
17 U-Boot can be run on a currently out-of-tree branch of QEMU with support for
18 the Boston board added. This QEMU code can currently be found in the "boston"
28 Please note that QEMU will default to emulating the I6400 CPU which implements
32 binary that will work in QEMU.
|
| H A D | README.nvme | 80 Testing NVMe with QEMU x86
82 QEMU supports NVMe emulation and we can test NVMe driver with QEMU x86 running
83 U-Boot. Please see README.x86 for how to build u-boot.rom image for QEMU x86.
85 Example command line to call QEMU x86 below with emulated NVMe device:
|
| /OK3568_Linux_fs/yocto/poky/ |
| H A D | README.qemu.md | 1 QEMU Emulation Targets
5 work with the QEMU emulator in system emulation mode. Several architectures
13 Use of the QEMU images is covered in the Yocto Project Reference Manual.
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/misc/ |
| H A 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.
|
| /OK3568_Linux_fs/kernel/Documentation/dev-tools/ |
| H A 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
|
| /OK3568_Linux_fs/buildroot/boot/edk2/ |
| H A D | Config.in | 46 Platform configuration for QEMU targeting the Virt machine.
54 Platform configuration for QEMU targeting the Virt machine.
97 bool "QEMU SBSA"
102 Platform configuration for QEMU targeting the SBSA reference
105 comment "QEMU SBSA depends on ATF not using EDK2 as BL33"
|
| /OK3568_Linux_fs/yocto/poky/documentation/sdk-manual/ |
| H A D | intro.rst | 62 - The Quick EMUlator (QEMU), which lets you simulate target hardware.
63 QEMU is not literally part of the SDK. You must build and include
64 this emulator separately. However, QEMU plays an important role in
128 The QEMU Emulator
131 The QEMU emulator allows you to simulate your hardware while running
132 your application or image. QEMU is not part of the SDK but is
185 using the QEMU emulator, go to the
194 To use the root filesystem in QEMU, you need to extract it. See the
200 and use the QEMU emulator, you can go to `QEMU Home
203 Yocto Project Development Tasks Manual for information on using QEMU
|
| /OK3568_Linux_fs/kernel/Documentation/virt/kvm/ |
| H A D | running-nested-guests.rst | 152 model supported by QEMU. e.g.::
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
238 - QEMU command-line of L1 -- when using libvirt, you'll find it here:
241 - QEMU command-line of L2 -- as above, when using libvirt, get the
[all …]
|
| /OK3568_Linux_fs/u-boot/board/emulation/qemu-x86/ |
| H A D | MAINTAINERS | 1 QEMU X86 BOARD
10 QEMU X86 64-bit BOARD
|
| /OK3568_Linux_fs/kernel/Documentation/bpf/ |
| H A 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>`_
|
| /OK3568_Linux_fs/yocto/poky/meta-skeleton/recipes-baremetal/baremetal-examples/ |
| H A D | baremetal-helloworld_git.bb | 1 SUMMARY = "Baremetal examples to work with the several QEMU architectures supported on OpenEmbedded"
3 DESCRIPTION = "These are introductory examples to showcase the use of QEMU to run baremetal applica…
28 # machine that QEMU uses on OE, e.g. -machine virt -cpu cortex-a57
|
| /OK3568_Linux_fs/u-boot/arch/x86/cpu/qemu/ |
| H A D | Kconfig | 7 config QEMU config
17 if QEMU
|
| /OK3568_Linux_fs/kernel/Documentation/openrisc/ |
| H A 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
|
| /OK3568_Linux_fs/kernel/drivers/platform/goldfish/ |
| H A D | Kconfig | 14 tristate "Goldfish virtual device for QEMU pipes"
16 This is a virtual device to drive the QEMU pipe interface used by
|
| /OK3568_Linux_fs/yocto/poky/meta/recipes-devtools/qemu/qemu/ |
| H A D | 0006-chardev-connect-socket-to-a-spawned-command.patch | 6 The command is started in a shell (sh -c) with stdin connect to QEMU
7 via a Unix domain stream socket. QEMU then exchanges data via its own
28 Another usage is starting swtpm from inside QEMU. swtpm will
30 QEMU, so there is no risk of lingering processes:
36 The patch was discussed upstream, but QEMU developers believe that the
37 code calling QEMU should be responsible for managing additional
|
| /OK3568_Linux_fs/buildroot/board/qemu/aarch64-sbsa/ |
| H A D | readme.txt | 4 The QEMU sbsa-ref machine is primarily meant for firmware development
28 Note that if you want to run sbsa-ref emulation with QEMU provided by
|
| /OK3568_Linux_fs/kernel/Documentation/ABI/testing/ |
| H A 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.
66 QEMU developers have traditionally used path name semantics
|
| /OK3568_Linux_fs/buildroot/package/slirp/ |
| H A D | Config.in | 19 - during that period, QEMU (Fabrice BELLARD) forked the code
20 and included it in QEMU
|
| /OK3568_Linux_fs/kernel/Documentation/admin-guide/mm/ |
| H A D | userfaultfd.rst | 189 QEMU/KVM
192 QEMU/KVM is using the ``userfaultfd`` syscall to implement postcopy live
198 migration to QEMU.
215 The QEMU in the source node writes all pages that it knows are missing
217 the QEMU running in the destination node runs ``UFFDIO_COPY|ZEROPAGE``
226 by the parallel QEMU migration thread).
228 After the QEMU postcopy thread (running in the destination node) gets
230 into the socket. The QEMU source node receives the information and
234 migration thread in the QEMU running in the destination node will
240 By the time the userfaults start, the QEMU in the destination node
[all …]
|