/qemu/docs/devel/ |
H A D | codebase.rst | 5 This section presents the various parts of QEMU and how the codebase is 12 ---------- 15 `MAINTAINERS <https://gitlab.com/qemu-project/qemu/-/blob/master/MAINTAINERS>`_ 18 Some of the main QEMU subsystems are: 20 - `Accelerators<Accelerators>` 21 - Block devices and `disk images<disk images>` support 22 - `CI<ci>` and `Tests<testing>` 23 - `Devices<device-emulation>` & Board models 24 - `Documentation <documentation-root>` 25 - `GDB support<GDB usage>` [all …]
|
H A D | code-of-conduct.rst | 6 The QEMU community is made up of a mixture of professionals and 11 * Be welcoming. We are committed to making participation in this project 12 a harassment-free experience for everyone, regardless of level of 18 social and technical, happen all the time and the QEMU community is no 21 QEMU community should be respectful when dealing with other contributors as 22 well as with people outside the QEMU community and with users of QEMU. 43 This code of conduct applies to all spaces managed by the QEMU project. 45 events, and any other forums created by the project team which the 48 member of the project or its community. 50 By adopting this code of conduct, project maintainers commit themselves [all …]
|
H A D | maintainers.rst | 6 Maintainers are a critical part of the project's contributor ecosystem. 8 working in their spare time to employees who work on the project as 11 - reviewing patches and suggesting changes 12 - collecting patches and preparing pull requests 13 - tending to the long term health of their area 14 - participating in other project activities 18 to project's :ref:`code_of_conduct` and should also be exemplars of 22 -------------------- 25 <https://gitlab.com/qemu-project/qemu/-/blob/master/MAINTAINERS>`__ 34 .. list-table:: Meaning of support status in MAINTAINERS [all …]
|
/qemu/ |
H A D | .gitmodules | 3 url = https://gitlab.com/qemu-project/seabios.git/ 6 url = https://gitlab.com/qemu-project/SLOF.git 9 url = https://gitlab.com/qemu-project/ipxe.git 12 url = https://gitlab.com/qemu-project/openbios.git 13 [submodule "roms/qemu-palcode"] 14 path = roms/qemu-palcode 15 url = https://gitlab.com/qemu-project/qemu-palcode.git 16 [submodule "roms/u-boot"] 17 path = roms/u-boot 18 url = https://gitlab.com/qemu-project/u-boot.git [all …]
|
H A D | .gitlab-ci.yml | 2 # This is the GitLab CI configuration file for the mainstream QEMU 3 # project: https://gitlab.com/qemu-project/qemu/-/pipelines 9 # To use a different set of jobs than the mainstream QEMU project, 12 # https://docs.gitlab.com/ee/ci/pipelines/settings.html#custom-cicd-configuration-path 14 # ---------------------------------------------------------------------- 16 # QEMU CI jobs are based on templates. Some templates provide 17 # user-configurable options, modifiable via configuration variables. 19 # See https://qemu-project.gitlab.io/qemu/devel/ci.html#custom-ci-cd-variables 24 - local: '/.gitlab-ci.d/qemu-project.yml'
|
H A D | README.rst | 2 QEMU README 5 QEMU is a generic and open source machine & userspace emulator and 8 QEMU is capable of emulating a complete machine in software without any 10 it achieves very good performance. QEMU can also integrate with the Xen 12 hypervisor to manage the CPU. With hypervisor support, QEMU can achieve 13 near native performance for CPUs. When QEMU emulates CPUs directly it is 17 QEMU is also capable of providing userspace API virtualization for Linux 23 QEMU aims to fit into a variety of use cases. It can be invoked directly 28 open source applications such as oVirt, OpenStack and virt-manager. 30 QEMU as a whole is released under the GNU General Public License, [all …]
|
H A D | .patchew.yml | 1 --- 6 # Patchew configuration is available to project administrators at 81 Patchew URL: https://patchew.org/QEMU/{{ obj.message_id }}/ 91 {% elif test == "docker-mingw@fedora" or test == "docker-quick@centos8" or test == "asan" %} 115 --- 117 Please send your feedback to patchew-devel@redhat.com 126 time make docker-test-debug@fedora TARGET_LIST=x86_64-softmmu J=14 NETWORK=1 127 docker-quick@centos8: 133 time make docker-test-quick@centos8 SHOW_ENV=1 J=14 NETWORK=1 140 git rev-parse base > /dev/null || exit 0 [all …]
|
/qemu/.github/workflows/ |
H A D | lockdown.yml | 1 # Configuration for Repo Lockdown - https://github.com/dessant/repo-lockdown 10 pull-requests: write 14 runs-on: ubuntu-latest 16 - uses: dessant/repo-lockdown@v2 18 pr-comment: | 19 Thank you for your interest in the QEMU project. 21 This repository is a read-only mirror of the project's repostories hosted 22 on https://gitlab.com/qemu-project/qemu.git. 23 The project does not process merge requests filed on GitHub. 25 QEMU welcomes contributions of code (either fixing bugs or adding new [all …]
|
/qemu/.gitlab-ci.d/custom-runners/ |
H A D | ubuntu-22.04-aarch64.yml | 1 # All ubuntu-22.04 jobs should run successfully in an environment 2 # setup by the scripts/ci/setup/ubuntu/build-environment.yml task 3 # "Install basic packages to build QEMU on Ubuntu 22.04" 5 ubuntu-22.04-aarch64-all-linux-static: 10 - ubuntu_22.04 11 - aarch64 13 - if: '$CI_PROJECT_NAMESPACE == "qemu-project" && $CI_COMMIT_BRANCH =~ /^staging/' 14 - if: "$AARCH64_RUNNER_AVAILABLE" 16 - mkdir build 17 - cd build [all …]
|
H A D | ubuntu-22.04-s390x.yml | 1 # All ubuntu-22.04 jobs should run successfully in an environment 2 # setup by the scripts/ci/setup/ubuntu/build-environment.yml task 3 # "Install basic packages to build QEMU on Ubuntu 22.04" 5 ubuntu-22.04-s390x-all-linux: 10 - ubuntu_22.04 11 - s390x 13 - if: '$CI_PROJECT_NAMESPACE == "qemu-project" && $CI_COMMIT_BRANCH =~ /^staging/' 14 - if: "$S390X_RUNNER_AVAILABLE" 16 - mkdir build 17 - cd build [all …]
|
/qemu/pc-bios/ |
H A D | README | 1 - SeaBIOS (bios.bin) is the successor of pc bios. 4 - The VGA BIOS and the Cirrus VGA BIOS come from the LGPL VGA bios 5 project (http://www.nongnu.org/vgabios/). 7 - OpenBIOS (http://www.openbios.org/) is a free (GPL v2) portable 9 1275-1994 (referred to as Open Firmware) compliant firmware. 11 Sparc32 (including QEMU,tcx.bin and QEMU,cgthree.bin) and Sparc64 are built 14 - SLOF (Slimline Open Firmware) is a free IEEE 1275 Open Firmware 16 https://gitlab.com/slof/slof, and the image currently in qemu is 17 built from git tag qemu-slof-20241106. 19 - VOF (Virtual Open Firmware) is a minimalistic firmware to work with [all …]
|
/qemu/docs/ |
H A D | conf.py | 1 # -*- coding: utf-8 -*- 3 # QEMU documentation build configuration file, created by 4 # sphinx-quickstart on Thu Jan 31 16:40:14 2019. 8 # for each of QEMU's manuals: in this case sphinx-build is run multiple 11 # the manuals into a single document: in this case sphinx-build is 12 # run once, on the top-level docs directory. 14 # QEMU's makefiles take option (1), which allows us to install 16 # to ship the 'devel' manual to end-users). 17 # Third-party sites such as readthedocs.org will take option (2). 34 # The per-manual conf.py will set qemu_docdir for a single-manual build; [all …]
|
/qemu/python/ |
H A D | PACKAGE.rst | 1 QEMU Python Tooling 4 This package provides QEMU tooling used by the QEMU project to build, 5 configure, and test QEMU. It is not a fully-fledged SDK and it is subject 9 ----- 11 The ``qemu.qmp`` subpackage provides a library for communicating with 12 QMP servers. The ``qemu.machine`` subpackage offers rudimentary 13 facilities for launching and managing QEMU processes. Refer to each 15 (``>>> help(qemu.qmp)``, ``>>> help(qemu.machine)``) 19 ------------ 22 the QEMU source tree. Contributions are welcome and follow the `QEMU [all …]
|
/qemu/.gitlab-ci.d/ |
H A D | opensbi.yml | 1 # All jobs needing docker-opensbi must use the same rules it uses. 5 - if: '$QEMU_CI != "1" && $QEMU_CI != "2" && $CI_PROJECT_NAMESPACE != "qemu-project"' 10 - if: '$QEMU_CI == "1" && $CI_PROJECT_NAMESPACE != "qemu-project"' 12 - .gitlab-ci.d/opensbi.yml 13 - .gitlab-ci.d/opensbi/Dockerfile 14 - roms/opensbi/* 19 …- if: '$QEMU_CI == "1" && $CI_PROJECT_NAMESPACE != "qemu-project" && $CI_COMMIT_REF_NAME =~ /^open… 24 …- if: '$QEMU_CI == "1" && $CI_PROJECT_NAMESPACE != "qemu-project" && $CI_COMMIT_MESSAGE =~ /opensb… 28 - if: '$CI_PROJECT_NAMESPACE == $QEMU_CI_UPSTREAM && $CI_PIPELINE_SOURCE == "schedule"' 32 - changes: [all …]
|
H A D | qemu-project.yml | 1 # This file contains the set of jobs run by the QEMU project: 2 # https://gitlab.com/qemu-project/qemu/-/pipelines 9 - $RUNNER_TAG 12 - local: '/.gitlab-ci.d/base.yml' 13 - local: '/.gitlab-ci.d/stages.yml' 14 - local: '/.gitlab-ci.d/opensbi.yml' 15 - local: '/.gitlab-ci.d/containers.yml' 16 - local: '/.gitlab-ci.d/crossbuilds.yml' 17 - local: '/.gitlab-ci.d/buildtest.yml' 18 - local: '/.gitlab-ci.d/static_checks.yml' [all …]
|
/qemu/docs/about/ |
H A D | build-platforms.rst | 1 .. _Supported-build-platforms: 6 QEMU aims to support building and executing on multiple host OS 9 minimum required versions of 3rd party software QEMU depends on. The 11 the project when patches are submitted for review, and tested before and 14 If a platform is not listed here, it does not imply that QEMU won't 21 support targets, QEMU considers only the version number, and assumes the 24 software in their distro, QEMU upstream code will not add explicit 25 support for those backports, unless the feature is auto-detectable in a 33 :ref:`setup-build-env` page. 36 ---------------------------- [all …]
|
/qemu/scripts/ci/ |
H A D | gitlab-pipeline-status | 3 # Copyright (c) 2019-2020 Red Hat, Inc. 9 # later. See the COPYING file in the top-level directory. 38 result = subprocess.run(['git', 'rev-parse', branch], 74 # project + commit. If this assumption is false, we can add further 77 msg = "No pipeline found for project %s and commit %s" % (project_id, 91 msg = ("Timeout (-t/--timeout) of %i seconds reached, " 122 prog='pipeline-status', 125 parser.add_argument('-t', '--timeout', type=int, default=7200, 129 parser.add_argument('-i', '--interval', type=int, default=60, 133 parser.add_argument('-w', '--wait', action='store_true', default=False, [all …]
|
/qemu/include/qemu/ |
H A D | help-texts.h | 4 /* Copyright string for -version arguments, About dialogs, etc */ 5 #define QEMU_COPYRIGHT "Copyright (c) 2003-2025 " \ 6 "Fabrice Bellard and the QEMU Project developers" 8 /* Bug reporting information for --help arguments, About dialogs, etc */ 10 "See <https://qemu.org/contribute/report-a-bug> for how to report bugs.\n" \ 11 "More information on the QEMU project at <https://qemu.org>."
|
/qemu/.gitlab-ci.d/cirrus/ |
H A D | README.rst | 5 While it is possible to provide private runners for non-Linux platforms this 9 offering: more specifically, we use the `cirrus-run`_ script to trigger Cirrus 13 There is, however, some one-time setup required. If you want FreeBSD and macOS 16 * set up a GitHub repository for the project, eg. ``yourusername/qemu``. 17 This repository needs to exist for cirrus-run to work, but it doesn't need to 28 for Cirrus CI to properly recognize the project. You can check whether 29 Cirrus CI knows about your project by navigating to: 31 ``https://cirrus-ci.com/yourusername/qemu`` 37 created earlier, eg. ``yourusername/qemu``; 44 general you'll want to be able to trigger Cirrus CI builds from non-protected [all …]
|
/qemu/docs/system/devices/ |
H A D | can.rst | 22 open-source/design/hardware solution. The core designer 23 of the project is Ondrej Ille, the financial support has been 26 The project has been initially started in frame of RTEMS GSoC 2013 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:: [all …]
|
/qemu/tests/functional/ |
H A D | test_ppc64_reverse_debug.py | 3 # SPDX-License-Identifier: GPL-2.0-or-later 13 # later. See the COPYING file in the top-level directory. 24 @skipFlakyTest("https://gitlab.com/qemu-project/qemu/-/issues/1992") 33 @skipFlakyTest("https://gitlab.com/qemu-project/qemu/-/issues/1992")
|
H A D | test_rx_gdbsim.py | 11 # later. See the COPYING file in the top-level directory. 24 ('https://github.com/philmd/qemu-testing-blob/raw/rx-gdbsim/rx/gdbsim/' 25 'u-boot.bin'), 28 ('https://github.com/philmd/qemu-testing-blob/raw/rx-gdbsim/rx/gdbsim/' 29 'rx-gdbsim.dtb'), 32 ('https://github.com/philmd/qemu-testing-blob/raw/rx-gdbsim/rx/gdbsim/' 38 U-Boot and checks that the console is operational. 40 self.set_machine('gdbsim-r5f562n8') 45 self.vm.add_args('-bios', uboot_path, 46 '-no-reboot') [all …]
|
/qemu/docs/devel/testing/ |
H A D | ci.rst | 11 Most of QEMU's CI is run on GitLab's infrastructure although a number 14 `project wiki testing page <https://wiki.qemu.org/Testing/CI>`_. 21 On QEMU, the gating process happens during the pull request. The approval is 22 done by the project leader running its own set of tests. The pull request gets 25 .. include:: ci-jobs.rst.inc 26 .. include:: ci-runners.rst.inc 29 ----------
|
H A D | ci-runners.rst.inc | 11 be set up with GitLab's "agent", called gitlab-runner, which will take 14 gitlab-runner, is called a "custom runner". 18 .gitlab-ci.d/custom-runners.yml 21 currently deployed in the QEMU GitLab CI and their maintainers, please 22 refer to the QEMU `wiki <https://wiki.qemu.org/AdminContacts>`__. 25 ------------------- 44 The ``scripts/ci/setup/$DISTRO/build-environment.yml`` Ansible 46 builds and run QEMU tests. This playbook consists on the installation 55 ansible-playbook -i inventory $DISTRO/build-environment.yml 59 by ``sudo``. If necessary, please refer to ``ansible-playbook`` [all …]
|
H A D | main.rst | 3 Testing in QEMU 6 QEMU's testing infrastructure is fairly complex as it covers 7 everything from unit testing and exercising specific sub-systems all 9 tests you can run ``make check-help`` from either the source or build 16 [./pyvenv/bin/]meson test --suite qemu:softfloat 38 ------------------------- 40 The "make check" testing family includes most of the C based tests in QEMU. 49 Different sub-types of "make check" tests will be explained below. 51 Before running tests, it is best to build QEMU programs first. Some tests 55 .. _unit-tests: [all …]
|