| /qemu/docs/system/ |
| H A D | target-riscv.rst | 1 .. _RISC-V-System-emulator:
3 RISC-V System emulator
6 QEMU can emulate both 32-bit and 64-bit RISC-V CPUs. Use the
7 ``qemu-system-riscv64`` executable to simulate a 64-bit RISC-V machine,
8 ``qemu-system-riscv32`` executable to simulate a 32-bit RISC-V machine.
10 QEMU has generally good support for RISC-V guests. It has support for
12 RISC-V hardware is much more widely varying than x86 hardware. RISC-V
13 CPUs are generally built into "system-on-chip" (SoC) designs created by
23 ----------------------
25 For QEMU's RISC-V system emulation, you must specify which board
[all …]
|
| H A D | target-mips.rst | 1 .. _MIPS-System-emulator:
3 MIPS System emulator
4 --------------------
6 Four executables cover simulation of 32 and 64-bit MIPS systems in both
7 endian options, ``qemu-system-mips``, ``qemu-system-mipsel``
8 ``qemu-system-mips64`` and ``qemu-system-mips64el``. Five different
11 - The MIPS Malta prototype board \"malta\"
13 - An ACER Pica \"pica61\". This machine needs the 64-bit emulator.
15 - MIPS emulator pseudo board \"mipssim\"
17 - A MIPS Magnum R4000 machine \"magnum\". This machine needs the
[all …]
|
| H A D | target-arm.rst | 1 .. _ARM-System-emulator:
3 Arm System emulator
4 -------------------
6 QEMU can emulate both 32-bit and 64-bit Arm CPUs. Use the
7 ``qemu-system-aarch64`` executable to simulate a 64-bit Arm machine.
8 You can use either ``qemu-system-arm`` or ``qemu-system-aarch64``
9 to simulate a 32-bit Arm machine: in general, command lines that
10 work for ``qemu-system-arm`` will behave the same when used with
11 ``qemu-system-aarch64``.
13 QEMU has generally good support for Arm guests. It has support for
[all …]
|
| H A D | target-avr.rst | 1 .. _AVR-System-emulator:
3 AVR System emulator
4 -------------------
6 Use the executable ``qemu-system-avr`` to emulate a AVR 8 bit based machine.
12 These boards use a ATmega controller, which model is limited to USART & 16-bit
14 https://github.com/seharris/qemu-avr-tests/blob/master/free-rtos/Demo/AVR_ATMega2560_GCC/demo.elf
20 - Continuous non interrupted execution::
22 qemu-system-avr -machine mega2560 -bios demo.elf
24 - Continuous non interrupted execution with serial output into telnet window::
26 qemu-system-avr -M mega2560 -bios demo.elf -nographic \
[all …]
|
| H A D | target-rx.rst | 1 .. _RX-System-emulator:
3 RX System emulator
4 --------------------
6 Use the executable ``qemu-system-rx`` to simulate RX target (GDB simulator).
9 - R5F562N8 MCU
11 - On-chip memory (ROM 512KB, RAM 96KB)
12 - Interrupt Control Unit (ICUa)
13 - 8Bit Timer x 1CH (TMR0,1)
14 - Compare Match Timer x 2CH (CMT0,1)
15 - Serial Communication Interface x 1CH (SCI0)
[all …]
|
| H A D | target-openrisc.rst | 1 .. _OpenRISC-System-emulator:
3 OpenRISC System emulator
6 QEMU can emulate 32-bit OpenRISC CPUs using the ``qemu-system-or1k`` executable.
8 OpenRISC CPUs are generally built into "system-on-chip" (SoC) designs that run
10 (the original OpenRISC instruction level simulator) which QEMU supports. For
11 this reason QEMU does not need to support many different boards to support the
14 The OpenRISC CPU supported by QEMU is the ``or1200``, it supports an MMU and can
20 For QEMU's OpenRISC system emulation, you must specify which board model you
21 want to use with the ``-M`` or ``--machine`` option; the default machine is
22 ``or1k-sim``.
[all …]
|
| H A D | introduction.rst | 7 ---------------------------
9 QEMU's system emulation provides a virtual model of a machine (CPU,
14 .. list-table:: Supported Accelerators
15 :header-rows: 1
17 * - Accelerator
18 - Host OS
19 - Host Architectures
20 * - KVM
21 - Linux
22 - Arm (64 bit only), MIPS, PPC, RISC-V, s390x, x86
[all …]
|
| H A D | security.rst | 5 --------
7 This chapter explains the security requirements that QEMU is designed to meet
8 and principles for securely deploying QEMU.
11 ---------------------
13 QEMU supports many different use cases, some of which have stricter security
24 safely on the physical CPU at close-to-native speed.
29 - Guest
30 - User-facing interfaces (e.g. VNC, SPICE, WebSocket)
31 - Network protocols (e.g. NBD, live migration)
32 - User-supplied files (e.g. disk images, kernels, device trees)
[all …]
|
| /qemu/.gitlab-ci.d/ |
| H A D | buildtest.yml | 2 - local: '/.gitlab-ci.d/buildtest-template.yml'
4 build-system-alpine:
6 - .native_build_job_template
7 - .native_build_artifact_template
9 - job: amd64-alpine-container
12 TARGETS: avr-softmmu loongarch64-softmmu mips64-softmmu mipsel-softmmu
13 MAKE_CHECK_ARGS: check-build
14 CONFIGURE_ARGS: --enable-docs --enable-trace-backends=log,simple,syslog
16 check-system-alpine:
19 - job: build-system-alpine
[all …]
|
| /qemu/docs/about/ |
| H A D | emulation.rst | 4 QEMU's Tiny Code Generator (TCG) provides the ability to emulate a
6 :ref:`System Emulation` and :ref:`User Mode Emulation` are supported
9 .. list-table:: Supported Guest Architectures for Emulation
11 :header-rows: 1
13 * - Architecture (qemu name)
14 - System
15 - User
16 - Notes
17 * - Alpha
18 - Yes
[all …]
|
| /qemu/docs/system/ppc/ |
| H A D | ppce500.rst | 4 QEMU for PPC supports a special ``ppce500`` machine designed for emulation and
8 -----------------
19 * Power-off functionality via one GPIO pin
26 ----------------------------------
29 which it passes to the guest, if there is no ``-dtb`` option. This provides
31 the various devices in the system.
33 If users want to provide their own DTB, they can use the ``-dtb`` option.
36 * The number of subnodes under /cpus node should match QEMU's ``-smp`` option
37 * The /memory reg size should match QEMU’s selected ram_size via ``-m``
39 Both ``qemu-system-ppc`` and ``qemu-system-ppc64`` provide emulation for the
[all …]
|
| /qemu/docs/system/devices/ |
| H A D | can.rst | 6 can be connected to host system CAN API (at this time only Linux
22 open-source/design/hardware solution. The core designer
31 to work on CAN hardware emulation on QEMU.
34 ----------------------------------------------------------
35 When QEMU with CAN PCI support is compiled then one of the next
38 (1) CAN bus Kvaser PCI CAN-S (single SJA1000 channel) board. QEMU startup options::
40 -object can-bus,id=canbus0
41 -device kvaser_pci,canbus=canbus0
43 Add "can-host-socketcan" object to connect device to host system CAN bus::
45 -object can-host-socketcan,id=canhost0,if=can0,canbus=canbus0
[all …]
|
| /qemu/docs/ |
| H A D | glossary.rst | 3 --------
5 --------
8 by QEMU developers.
11 -----------
14 hardware-based, through a virtualization API provided by the host OS (kvm, hvf,
15 whpx, ...), or software-based (tcg). See this description of `supported
19 -----
24 -----
26 Block drivers are the available `disk formats and front-ends
27 <block-drivers>` available, and block devices `(see Block device section on
[all …]
|
| /qemu/ |
| H A D | MAINTAINERS | 1 QEMU Maintainers
10 consult qemu-devel and not any specific individual privately.
23 W: Web-page with status/info
24 Q: Patchwork web based patch tracking system site
34 it has been replaced by a better system and you
59 ------------------------------
63 L: qemu-devel@nongnu.org
72 R: Philippe Mathieu-Daudé <philmd@linaro.org>
73 W: https://www.qemu.org/docs/master/devel/index.html
75 F: docs/devel/build-environment.rst
[all …]
|
| /qemu/target/loongarch/ |
| H A D | README | 1 - Introduction
7 …https://github.com/loongson/LoongArch-Documentation/releases/download/2021.08.17/LoongArch-Vol1-v1…
9 …We can get the latest loongarch documents at https://github.com/loongson/LoongArch-Documentation/t…
12 - System emulation
14 …You can reference docs/system/loongarch/loongson3.rst to get the information about system emulatio…
16 - Linux-user emulation
18 …We already support Linux user emulation. We can use LoongArch cross-tools to build LoongArch execu…
19 and We can also use qemu-loongarch64 to run LoongArch executables.
21 1. Config cross-tools env.
23 see System emulation.
[all …]
|
| /qemu/docs/system/riscv/ |
| H A D | virt.rst | 8 real-world hardware.
11 -----------------
17 * Platform-Level Interrupt Controller (PLIC)
22 * 8 virtio-mmio transport devices
24 * The fw_cfg device that allows a guest to obtain data from QEMU
31 ----------------------------------
34 which it passes to the guest, if there is no ``-dtb`` option. This provides
36 the various devices in the system. Guest software should discover the devices
39 If users want to provide their own DTB, they can use the ``-dtb`` option.
42 * The number of subnodes of the /cpus node should match QEMU's ``-smp`` option
[all …]
|
| /qemu/docs/devel/ |
| H A D | build-system.rst | 2 The QEMU build system architecture
6 QEMU build system. As with projects using GNU autotools, the QEMU build
7 system has two stages; first the developer runs the "configure" script
14 - build artifacts outside of QEMU source tree entirely::
19 ../qemu/configure
22 - build artifacts in a subdir of QEMU source tree::
38 - detect the host architecture
40 - list the targets for which to build emulators; the list of
43 - find the compilers (native and cross) used to build executables,
45 fragments (``config-host.mak``) or a Meson machine file
[all …]
|
| /qemu/.gitlab/issue_templates/ |
| H A D | bug.md | 1 <!--
2 This is the upstream QEMU issue tracker.
5 to reproduce the problem with the latest qemu.git master built from
6 source. See https://www.qemu.org/download/#source for instructions on
9 QEMU generally supports the last two releases advertised on
10 https://www.qemu.org/. Problems with distro-packaged versions of QEMU
13 See https://www.qemu.org/contribute/report-a-bug/ for additional
17 https://www.qemu.org/contribute/security-process/
18 -->
21 - Operating system: <!-- Windows 10 21H1, Fedora 37, etc. -->
[all …]
|
| /qemu/tests/multiboot/ |
| H A D | aout_kludge.out | 22 qemu-system-x86_64: invalid load_addr address
27 qemu-system-x86_64: invalid load_end_addr address
32 qemu-system-x86_64: invalid header_addr address
37 qemu-system-x86_64: invalid bss_end_addr address
42 qemu-system-x86_64: kernel does not fit in address space
|
| /qemu/docs/system/arm/ |
| H A D | sbsa.rst | 1 Arm Server Base System Architecture Reference board (``sbsa-ref``)
4 The ``sbsa-ref`` board intends to look like real hardware (while the ``virt``
9 - `Base System Architecture <https://developer.arm.com/documentation/den0094/>`__ (BSA)
10 - `Server Base System Architecture <https://developer.arm.com/documentation/den0029/>`__ (SBSA)
13 specification defines how the firmware reports that to any operating system.
21 The ``sbsa-ref`` board supports:
23 - A configurable number of AArch64 CPUs
24 - GIC version 3
25 - System bus AHCI controller
26 - System bus XHCI controller
[all …]
|
| H A D | orangepi.rst | 1 Orange Pi PC (``orangepi-pc``)
4 The Xunlong Orange Pi PC is an Allwinner H3 System on Chip
5 based embedded computer with mainline support in both U-Boot
6 and Linux. The board comes with a Quad Core Cortex-A7 @ 1.3GHz,
15 * SMP (Quad Core Cortex-A7)
20 * Timer device (re-used from Allwinner A10)
26 * System Control module
36 - Graphical output via HDMI, GPU and/or the Display Engine
37 - Audio output
38 - Hardware Watchdog
[all …]
|
| H A D | cpu-features.rst | 5 choose to implement or not. In QEMU, optional CPU features have
10 Cortex-A15 and the Cortex-A57, which respectively implement Arm
11 architecture reference manuals ARMv7-A and ARMv8-A, may both optionally
12 implement PMUs. For example, if a user wants to use a Cortex-A15 without
13 a PMU, then the ``-cpu`` parameter should contain ``pmu=off`` on the QEMU
14 command line, i.e. ``-cpu cortex-a15,pmu=off``.
18 that implement the ARMv8-A architecture reference manual may optionally
20 ``aarch64`` CPU property. A CPU type such as the Cortex-A15, which does
21 not implement ARMv8-A, will not have the ``aarch64`` CPU property.
23 QEMU's support may be limited for some CPU features, only partially
[all …]
|
| /qemu/scripts/ |
| H A D | qemu-trace-stap | 2 # -*- python -*-
6 # QEMU SystemTap Trace Tool
31 return re.sub("-", ".", filename) + ".log"
76 script = """probe begin { print("Running script, <Ctrl>-c to quit\\n") } """ + script
79 # can be easily overflowed by frequently firing QEMU traces
80 stapargs = [stap, "-s", "8", "-I", tapsets ]
82 stapargs.extend(["-x", args.pid])
83 stapargs.extend(["-e", script])
101 proc = subprocess.Popen([stap, "-I", tapsets, "-l", script],
121 parser = argparse.ArgumentParser(description="QEMU SystemTap trace tool")
[all …]
|
| /qemu/rust/ |
| H A D | wrapper.h | 2 * QEMU System Emulator
38 * in QEMU code, so it's fine to declare dummy types instead.
50 #include "qemu/osdep.h"
51 #include "qemu/module.h"
52 #include "qemu-io.h"
53 #include "system/system.h"
55 #include "system/memory.h"
56 #include "chardev/char-fe.h"
58 #include "hw/qdev-clock.h"
59 #include "hw/qdev-properties.h"
[all …]
|
| /qemu/docs/user/ |
| H A D | main.rst | 1 .. _user-mode:
3 QEMU User space emulator
7 ---------------------------
11 - Linux (referred as qemu-linux-user)
13 - BSD (referred as qemu-bsd-user)
16 --------
18 QEMU user space emulation has the following notable features:
20 **System call translation:**
21 QEMU includes a generic system call translator. This means that the
22 parameters of the system calls can be converted to fix endianness and
[all …]
|