| /openbmc/qemu/python/ |
| H A D | README.rst | 1 QEMU Python Tooling
4 This directory houses Python tooling used by the QEMU project to build,
5 configure, and test QEMU. It is organized by namespace (``qemu``), and
6 then by package (e.g. ``qemu/machine``, ``qemu/qmp``, etc).
8 ``setup.py`` is used by ``pip`` to install this tooling to the current
9 environment. ``setup.cfg`` provides the packaging configuration used by
10 ``setup.py``. You will generally invoke it by doing one of the following:
17 2. ``pip3 install --user .`` will install these packages to your user's
21 If you append the ``--editable`` or ``-e`` argument to either invocation
23 a forwarder ("qemu.egg-link") that points to the source tree. In so
[all …]
|
| H A D | Makefile | 1 QEMU_VENV_DIR=.dev-venv
2 QEMU_MINVENV_DIR=.min-venv
9 @echo "make check-minreqs:"
15 @echo "make check-tox:"
18 @echo " Requires: Python 3.8 - 3.11, and tox."
19 @echo " Hint (Fedora): 'sudo dnf install python3-tox python3.11'"
23 @echo "make check-dev:"
30 @echo " Performs no environment setup of any kind."
34 @echo " and install the qemu package in editable mode."
37 @echo "make min-venv"
[all …]
|
| H A D | setup.py | 3 QEMU tooling installer script
4 Copyright (c) 2020-2021 John Snow for Red Hat, Inc.
17 This prevents calling 'setup.py install' directly, as the 'install'
23 'Installation directly via setup.py is not supported.\n'
30 QEMU tooling installer
33 # https://medium.com/@daveshawley/safely-using-setup-cfg-for-metadata-1babbe54c108
36 setuptools.setup(cmdclass={'bdist_egg': bdist_egg_guard})
|
| /openbmc/docs/ |
| H A D | cheatsheet.md | 11 meta-phosphor/common/recipes-kernel/linux/linux-obmc_X.Y.bb
30 $ . setup palmetto
31 $ bitbake obmc-phosphor-image
40 $ . setup zaius
41 $ bitbake obmc-phosphor-image
49 meta-<layer>/meta-<system>/conf/machine/machineA.conf
50 meta-<layer>/meta-<system>/conf/machine/machineB.conf
54 to the `setup`.
58 $ . setup machineB
59 $ bitbake obmc-phosphor-image
[all …]
|
| /openbmc/bmcweb/ |
| H A D | TESTING.md | 11 are the steps for using the SDK and QEMU.
13 - Follow all
14 …[development environment setup](https://github.com/openbmc/docs/blob/master/development/dev-enviro…
15 directions in the development environment setup document. This will get QEMU
17 - Follow all of the
18 [gerrit setup](https://github.com/openbmc/docs/blob/master/development/gerrit-setup.md)
19 directions in the gerrit setup document.
20 - Clone bmcweb from gerrit
26 - Follow directions in
29 - Reduce binary size by stripping it when ready for testing
[all …]
|
| /openbmc/openbmc-build-scripts/jenkins/ |
| H A D | README.md | 7 | --------------------------------- | ------------------------------- | ---------- |
8 | CI-MISC/ci-build-seed | jenkins/build-seed | |
9 | CI-MISC/ci-meta | jenkins/run-meta-ci | Deprecated |
10 | CI-MISC/ci-openbmc-build-scripts | jenkins/run-build-script-ci | |
11 | CI-MISC/ci-repository-ppc64le | run-unit-test-docker.sh | |
12 | CI-MISC/openbmc-node-cleaner | sstate-cache-management.sh | [1] |
13 | CI-MISC/openbmc-userid-validation | jenkins/userid-validation | |
14 | CI-MISC/run-ci-in-qemu | run-qemu-robot-test.sh | |
15 | ci-openbmc | build-setup.sh | |
16 | ci-repository | run-unit-test-docker.sh | |
[all …]
|
| /openbmc/qemu/.gitlab-ci.d/ |
| H A D | crossbuild-template.yml | 4 image: $CI_REGISTRY_IMAGE/qemu/$IMAGE:$QEMU_CI_CONTAINER_TAG
7 - ccache
12 - source scripts/ci/gitlab-ci-section
13 - section_start setup "Pre-script setup"
14 - JOBS=$(expr $(nproc) + 1)
15 - cat /packages.txt
16 - section_end setup
18 - export CCACHE_BASEDIR="$(pwd)"
19 - export CCACHE_DIR="$CCACHE_BASEDIR/ccache"
20 - export CCACHE_MAXSIZE="500M"
[all …]
|
| /openbmc/docs/development/ |
| H A D | dev-environment.md | 16 [QEMU](https://www.qemu.org/).
19 distribution for a system. QEMU is a software emulator that can be used to run
23 development environment, building OpenBMC, and running that image in QEMU.
41 [VMware](https://www.vmware.com/products/workstation-player/workstation-player-evaluation.html)
51 [build-setup.sh](https://github.com/openbmc/openbmc-build-scripts/blob/master/build-setup.sh)
58 The majority of OpenBMC development community uses Ubuntu. The qemu below is
63 **VirtualBox Tips** - You'll want copy/paste working between your VM and
66 - Devices -> Insert Guest Additions CD Image (install)
67 - Devices -> Shared Clipboard -> Bidirectional
68 - reboot (the VM)
[all …]
|
| H A D | README.md | 7 1. [Development Environment Setup](dev-environment.md)
9 Start here. This shows how to setup an OpenBMC development environment using
10 its bitbake build process and how to start the software emulator, QEMU.
12 2. [Hello World](devtool-hello-world.md)
15 repository, build, and test your changes within QEMU.
17 3. [Web UI Development](web-ui.md)
19 This shows how to modify the phosphor-webui web application and test your
20 changes within QEMU.
22 4. [Code Reviews Using Gerrit](gerrit-setup.md)
24 This shows how to setup your environment to utilize Gerrit for submitting
|
| H A D | devtool-hello-world.md | 4 in QEMU.
6 **Prerequisites:** Completed Development Environment Setup
7 [Document](https://github.com/openbmc/docs/blob/master/development/dev-environment.md)
16 [phosphor-state-manager](https://github.com/openbmc/phosphor-state-manager.git)
20 environment, right after doing the ". setup" command.
25 devtool modify phosphor-state-manager
33 vi workspace/sources/phosphor-state-manager/bmc_state_manager_main.cpp
43 @@ -17,6 +18,8 @@ int main(int argc, char**)
59 bitbake obmc-phosphor-image
62 Follow the steps in the first tutorial to load your new image into a QEMU
[all …]
|
| /openbmc/qemu/docs/devel/testing/ |
| 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>`__.
24 Machine Setup Howto
25 -------------------
27 For all Linux based systems, the setup can be mostly automated by the
29 under ``scripts/ci/setup``, such as this::
44 The ``scripts/ci/setup/$DISTRO/build-environment.yml`` Ansible
[all …]
|
| /openbmc/qemu/docs/tools/ |
| H A D | qemu-pr-helper.rst | 2 QEMU persistent reservation helper
6 --------
8 **qemu-pr-helper** [*OPTION*]
11 -----------
13 Implements the persistent reservation helper for QEMU.
16 to specific initiators in a shared storage setup. When implementing
21 storage fabric. QEMU's SCSI passthrough devices ``scsi-block``
22 and ``scsi-generic`` support passing guest persistent reservation
23 requests to a privileged external helper program. :program:`qemu-pr-helper`
25 accept incoming connections for communication with QEMU.
[all …]
|
| /openbmc/qemu/tests/functional/qemu_test/ |
| H A D | testcase.py | 5 # Original Author (Avocado-based tests):
12 # later. See the COPYING file in the top-level directory.
23 from qemu.machine import QEMUMachine
24 from qemu.utils import kvm_available, tcg_available
40 def setUp(self, bin_prefix): member in QemuBaseTest
42 self.arch = self.qemu_bin.split('-')[-1]
51 self.log = logging.getLogger('qemu-test')
56 '%(asctime)s - %(levelname)s: %(message)s')
61 self.machinelog = logging.getLogger('qemu.machine')
72 path = os.path.basename(sys.argv[0])[:-3]
[all …]
|
| /openbmc/openbmc/poky/meta/lib/oeqa/selftest/cases/ |
| H A D | glibc.py | 4 # SPDX-License-Identifier: MIT
32 … features.append('EGLIBCPARALLELISM:task-check:pn-glibc-testsuite = "PARALLELMFLAGS="-j1""')
37 bitbake("glibc-testsuite -c check")
41 builddir = get_bb_var("B", "glibc-testsuite")
43 ptestsuite = "glibc-user" if ssh is None else "glibc"
44 self.ptest_section(ptestsuite, duration = int(end_time - start_time))
55 # build core-image-minimal with required packages
57 "glibc-charmaps",
63 # "python3-pexpect",
64 "nfs-utils",
[all …]
|
| /openbmc/qemu/tests/vm/ |
| H A D | freebsd | 5 # Copyright 2017-2019 Red Hat Inc.
12 # the COPYING file in the top-level directory.
31 …= "https://download.freebsd.org/releases/CI-IMAGES/14.1-RELEASE/amd64/Latest/FreeBSD-14.1-RELEASE-…
36 set -e;
37 rm -rf /home/qemu/qemu-test.*
38 cd $(mktemp -d /home/qemu/qemu-test.XXXXXX);
40 tar -xf /dev/vtbd1;
42 ../src/configure --extra-ldflags=-L/usr/local/lib \
43 --extra-cflags=-I/usr/local/include {configure_opts};
44 gmake --output-sync -j{jobs} {target} {verbose};
[all …]
|
| /openbmc/u-boot/board/imgtec/malta/ |
| H A D | lowlevel_init.S | 1 /* SPDX-License-Identifier: GPL-2.0 */
56 * 'MIPS: qemu-malta: add YAMON-style GT64120 memory map'
58 * http://www.mail-archive.com/barebox@lists.infradead.org/msg06128.html
60 * based on write_bootloader() in qemu.git/hw/mips_malta.c
61 * see GT64120 manual and qemu.git/hw/gt64xxx.c for details
69 /* setup MEM-to-PCI0 mapping */
72 /* setup PCI0 io window to 0x18000000-0x181fffff */
78 /* setup PCI0 mem windows */
96 /* setup peripheral bus controller clock divide */
118 /* setup basic address decode */
[all …]
|
| /openbmc/qemu/tests/qtest/libqos/ |
| H A D | igb.c | 4 * Copyright (c) 2022-2023 Red Hat, Inc.
20 #include "qemu/osdep.h"
25 #include "pci-pc.h"
26 #include "qemu/sockets.h"
27 #include "qemu/iov.h"
28 #include "qemu/module.h"
29 #include "qemu/bitops.h"
30 #include "libqos-malloc.h"
50 qpci_iounmap(&epci->pci_dev, epci->mac_regs); in e1000e_pci_destructor()
51 qpci_msix_disable(&epci->pci_dev); in e1000e_pci_destructor()
[all …]
|
| /openbmc/qemu/docs/system/ |
| H A D | tls.rst | 3 TLS setup for network services
4 ------------------------------
6 Almost all network services in QEMU have the ability to use TLS for
9 certificates suitable for usage with QEMU, and applies to the VNC
13 At a high level, QEMU requires certificates and private keys to be
23 At a minimum it is necessary to setup a certificate authority, and issue
28 Assuming that the QEMU network services will only ever be exposed to
30 certificate authority to create certificates. A self-signed CA is
32 ability of malicious 3rd parties to trick the CA into mis-issuing certs
40 ``/etc/pki/qemu`` or for unprivileged users in ``$HOME/.pki/qemu``.
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-graphics/graphviz/ |
| H A D | graphviz_12.2.0.bb | 3 LICENSE = "EPL-1.0"
7 bison-native \
8 groff-native \
10 gdk-pixbuf \
16 DEPENDS:append:class-target = " ${BPN}-native"
17 DEPENDS:append:class-nativesdk = " ${BPN}-native"
19 inherit autotools-brokensep pkgconfig gettext qemu
21 SRC_URI = "https://gitlab.com/api/v4/projects/4207231/packages/generic/${BPN}-releases/${PV}/${BP}.…
23 SRC_URI:append:class-nativesdk = "\
24 file://graphviz-setup.sh \
[all …]
|
| /openbmc/qemu/docs/system/devices/ |
| H A D | can.rst | 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
47 (2) CAN bus PCM-3680I PCI (dual SJA1000 channel) emulation::
[all …]
|
| /openbmc/openbmc-build-scripts/ |
| H A D | qemu-build.sh | 4 # This build script is for running the QEMU build in a container
6 # It expects to be run in with the qemu source present in the directory called
7 # '$WORKSPACE/qemu', where WORKSPACE is an environment variable.
9 # In Jenkins configure the git SCM 'Additional Behaviours', 'check-out to a sub
10 # directory' called 'qemu'.
12 # When building locally set WORKSPACE to be the directory above the qemu
14 # git clone https://github.com/qemu/qemu
15 # WORKSPACE=$PWD/qemu ~/openbmc-build-scripts/qemu-build.sh
21 # Default: "", proxy is not setup if this is not set
30 #set -x
[all …]
|
| /openbmc/qemu/.gitlab-ci.d/custom-runners/ |
| 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 …]
|
| /openbmc/qemu/docs/devel/ |
| H A D | vfio-iommufd.rst | 9 for assigned devices. While the legacy kernel interface is group-centric,
10 the new iommufd interface is device-centric, relying on device fd and iommufd.
12 To support both interfaces in the QEMU VFIO device, introduce a base container
18 specific to either legacy or iommufd. Each container has its own way to setup
25 +-------+ +----------+ +-----+ +-----+
27 +---+---+ +----+-----+ +--+--+ +--+--+ +----------------------+
29 | | | | +------------+---------+
30 +---V-----------V-----------V--------V----+ /
31 | VFIOAddressSpace | <------------+
34 +-------+----------------------------+----+
[all …]
|
| /openbmc/openbmc/poky/documentation/sdk-manual/ |
| H A D | intro.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
17 - *Cross-Development Toolchain*: This toolchain contains a compiler,
20 - *Libraries, Headers, and Symbols*: The libraries, headers, and
24 - *Environment Setup Script*: This ``*.sh`` file, once sourced, sets up the
25 cross-development environment by defining variables and preparing for
35 self-contained. The binaries are linked against their own copy of
42 Another feature of the SDKs is that only one set of cross-compiler
50 sysroot because those binaries are target-specific.
54 - The self-contained SDK, which is an architecture-specific
55 cross-toolchain and matching sysroots (target and native) all built
[all …]
|
| /openbmc/qemu/docs/specs/ |
| H A D | ivshmem-spec.rst | 2 Device Specification for Inter-VM shared memory device
5 The Inter-VM shared memory device (ivshmem) is designed to share a
6 memory region between multiple QEMU processes running different guests
8 shared memory area, it is modeled by QEMU as a PCI device exposing
17 For information on configuring the ivshmem device on the QEMU
24 QEMU 2.6.0, it had revision 0.
27 --------
31 - BAR0 holds device registers (256 Byte MMIO)
32 - BAR1 holds MSI-X table and PBA (only ivshmem-doorbell)
33 - BAR2 maps the shared memory object
[all …]
|