Searched +full:build +full:- +full:without +full:- +full:default +full:- +full:devices (Results 1 – 25 of 58) sorted by relevance
123
13 SCSI adapters. Arm, s390 and x86 boards can all present a virtio-blk16 Each QEMU target enables a subset of the boards, devices and buses that21 QEMU uses a simple domain-specific language to describe the dependencies24 * new targets and boards can be added without knowing in detail the27 include all the required dependencies and all the devices that the30 * users can easily build reduced versions of QEMU that support only a subset31 of boards or devices. For example, by default most targets will include32 all emulated PCI devices that QEMU supports, but the build process is36 This domain-specific language is based on the Kconfig language that41 is instead specified in per-target files under the ``configs/``[all …]
12 ----------15 `MAINTAINERS <https://gitlab.com/qemu-project/qemu/-/blob/master/MAINTAINERS>`_20 - `Accelerators<Accelerators>`21 - Block devices and `disk images<disk images>` support22 - `CI<ci>` and `Tests<testing>`23 - `Devices<device-emulation>` & Board models24 - `Documentation <documentation-root>`25 - `GDB support<GDB usage>`26 - :ref:`Migration<migration>`27 - `Monitor<QEMU monitor>`[all …]
1 # All ubuntu-22.04 jobs should run successfully in an environment2 # setup by the scripts/ci/setup/ubuntu/build-environment.yml task3 # "Install basic packages to build QEMU on Ubuntu 22.04"5 ubuntu-22.04-aarch64-all-linux-static:8 stage: build10 - ubuntu_22.0411 - aarch6413 - if: '$CI_PROJECT_NAMESPACE == "qemu-project" && $CI_COMMIT_BRANCH =~ /^staging/'14 - if: "$AARCH64_RUNNER_AVAILABLE"16 - mkdir build[all …]
5 This document describes the virtual-device fuzzing infrastructure in QEMU and9 ------16 is an *in-process* fuzzer. For the developer, this means that it is their17 responsibility to ensure that state is reset between fuzzing-runs.20 --------------------22 To build the fuzzers, install a recent version of clang:24 Here, enable-asan and enable-ubsan are optional but they allow us to reliably25 detect bugs such as out-of-bounds accesses, uses-after-free, double-frees28 CC=clang-8 CXX=clang++-8 /path/to/configure \29 --enable-fuzzing --enable-asan --enable-ubsan[all …]
7 everything from unit testing and exercising specific sub-systems all9 tests you can run ``make check-help`` from either the source or build13 the meson build system so can be run directly from the build tree,16 [./pyvenv/bin/]meson test --suite qemu:softfloat38 -------------------------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 tests55 .. _unit-tests:68 In QEMU, unit tests can be invoked with ``make check-unit``. They are76 1. Create a new source file. For example, ``tests/unit/foo-test.c``.[all …]
8 real-world hardware.10 Supported devices11 -----------------13 The ``virt`` machine supports the following devices:17 * Platform-Level Interrupt Controller (PLIC)22 * 8 virtio-mmio transport devices26 The hypervisor extension has been enabled for the default CPU, so virtual27 machines with hypervisor extension can simply be used without explicitly31 ----------------------------------34 which it passes to the guest, if there is no ``-dtb`` option. This provides[all …]
4 SiFive HiFive Unleashed Development Board is the ultimate RISC-V development5 board featuring the Freedom U540 multi-core RISC-V processor.7 Supported devices8 -----------------10 The ``sifive_u`` machine supports the following devices:15 * Platform-Level Interrupt Controller (PLIC)17 * L2 Loosely Integrated Memory (L2-LIM)22 * 1 One-Time Programmable (OTP) memory with stored serial number30 1 E51 core and 4 U54 core combination and the RISC-V core boots in 64-bit mode.32 is also possible to create a 32-bit variant with the same peripherals except[all …]
4 The Intel Query Processing Library (Intel ``QPL``) is an open-source library to8 The ``QPL`` compression relies on Intel In-Memory Analytics Accelerator(``IAA``)21 +----------------+ +------------------+22 | MultiFD Thread | |accel-config tool |23 +-------+--------+ +--------+---------+27 +-------+--------+ | Setup IAA29 +-------+---+----+ |31 | +-------------+-------+33 | Devices +-----+-----+35 | +-----+-----+[all …]
4 UADK is a general-purpose user space accelerator framework that uses shared8 UADK includes Unified/User-space-access-intended Accelerator Framework (UACCE),24 different character devices with UACCE by using kernel-mode drivers of the25 vendors. A user can access the hardware accelerators by performing user-mode26 operations on the character devices.30 +----------------------------------+32 +----+------------------------+----+35 +-------+--------+ +-------+-------+37 +-------+--------+ +-------+-------+41 | +--------+------+[all …]
20 QAT Devices: 421 |-----------|--------|---------|----------|----------|------|------|24 |-----------|--------|---------|----------|----------|------|------|26 |-----------|--------|---------|----------|----------|------|------|28 |-----------|--------|---------|----------|----------|------|------|30 |-----------|--------|---------|----------|----------|------|------|41 <https://github.com/intel/QATzip?tab=readme-ov-file#introductionl>`_45 +----------------+47 +-------+--------+50 +-------+--------+[all …]
14 source_path=$(cd "$(dirname -- "$0")"; pwd)16 if test "$PWD" -ef "$source_path"18 echo "Using './build' as the directory for build output"20 MARKER=build/auto-created-by-configure22 if test -e build24 if test -f $MARKER26 rm -rf build28 echo "ERROR: ./build dir already exists and was not previously created by configure"33 if ! mkdir build || ! touch $MARKER35 echo "ERROR: Could not create ./build directory. Check the permissions on"[all …]
15 meson.add_postconf_script(find_program('scripts/symlink-install-tree.py'))28 config_host = keyval.load(meson.current_build_dir() / 'config-host.mak')31 # configure runs. Since it is in the build directory35 tmpdir = meson.current_build_dir() / 'meson-private/temp'61 # type of binaries to build66 have_linux_user = have_linux_user or target.endswith('linux-user')67 have_bsd_user = have_bsd_user or target.endswith('bsd-user')68 have_system = have_system or target.endswith('-softmmu')113 …dgen.version() + ' is unsupported. You can install a new version with "cargo install bindgen-cli"')120 message('To use Rust you can install a new version with "cargo install bindgen-cli"')[all …]
6 PCIE-to-PCI bridge is a new method for legacy PCI9 Previously Intel DMI-to-PCI bridge was used for this purpose.10 But due to its strict limitations - no support of hot-plug,11 no cross-platform and cross-architecture support - a new generic12 PCIE-to-PCI bridge should now be used for any legacy PCI device usage15 This generic PCIE-PCI bridge is a cross-platform device,16 can be hot-plugged into appropriate root port (requires additional actions,17 see 'PCIE-PCI bridge hot-plug' section),18 and supports devices hot-plug into the bridge itself21 Hot-plug of legacy PCI devices into the bridge[all …]
1 Intel Graphics Device (IGD) assignment with vfio-pci4 Using vfio-pci, we can passthrough Intel Graphics Device (IGD) to guest, either7 support. However, IGD devices are not "clean" PCI devices, they use extra16 (*-Required by)19 |---------------------------------------------|-------|---------|-------|---------|30 For #1, the "x-igd-opregion=on" option exposes a copy of host IGD OpRegion to33 For #2, "x-igd-lpc=on" option copies the IDs of host LPC bridge and host bridge42 For #5, "x-vga=on" enables guest access to standard VGA IO/MMIO ranges.57 x-igd-opregion=on,x-igd-lpc=on,x-vga=on59 By default, "Legacy" mode won't fail, it continues on error. User can set[all …]
7 ---------------------------10 memory and emulated devices) to run a guest OS. It supports a number14 .. list-table:: Supported Accelerators15 :header-rows: 117 * - Accelerator18 - Host OS19 - Host Architectures20 * - KVM21 - Linux22 - Arm (64 bit only), MIPS, PPC, RISC-V, s390x, x86[all …]
7 ------------11 These AP devices provide cryptographic functions to all CPUs assigned to a19 -------------------------51 An AP queue is the means by which an AP command-request message is sent to an57 which the AP command-request message is to be sent for processing.63 * NQAP: to enqueue an AP command-request message to a queue64 * DQAP: to dequeue an AP command-reply message from a queue73 ----------------------------------------------84 an APID from 0-255. If a bit is set, the corresponding adapter is valid for89 corresponds to an AP queue index (APQI) from 0-255. If a bit is set, the[all …]
2 - local: '/.gitlab-ci.d/buildtest-template.yml'4 build-system-alpine:6 - .native_build_job_template7 - .native_build_artifact_template9 - job: amd64-alpine-container12 TARGETS: avr-softmmu loongarch64-softmmu mips64-softmmu mipsel-softmmu13 MAKE_CHECK_ARGS: check-build14 CONFIGURE_ARGS: --enable-docs --enable-trace-backends=log,simple,syslog16 check-system-alpine:19 - job: build-system-alpine[all …]
2 - local: '/.gitlab-ci.d/crossbuild-template.yml'4 cross-armhf-user:7 job: armhf-debian-cross-container9 IMAGE: debian-armhf-cross11 cross-arm64-system:14 job: arm64-debian-cross-container16 IMAGE: debian-arm64-cross18 cross-arm64-user:21 job: arm64-debian-cross-container23 IMAGE: debian-arm64-cross[all …]
1 Hyper-V Enlightenments6 -----------11 It may, however, be hard-to-impossible to add support for these interfaces to14 KVM on x86 implements Hyper-V Enlightenments for Windows guests. These features15 make Windows and Hyper-V guests think they're running on top of a Hyper-V16 compatible hypervisor and use Hyper-V specific features.20 -----22 No Hyper-V enlightenments are enabled by default by either KVM or QEMU. In25 .. parsed-literal::27 |qemu_system| --enable-kvm --cpu host,hv_relaxed,hv_vpindex,hv_time, ...[all …]
2 SPDX-License-Identifier: GPL-2.0-or-later4 virtio-gpu7 This document explains the setup and usage of the virtio-gpu device.8 The virtio-gpu device paravirtualizes the GPU and display controller.11 --------------------13 virtio-gpu requires a guest Linux kernel built with the16 QEMU virtio-gpu variants17 ------------------------19 QEMU virtio-gpu device variants come in the following form:21 * ``virtio-vga[-BACKEND]``[all …]
22 open-source/design/hardware solution. The core designer34 ----------------------------------------------------------38 (1) CAN bus Kvaser PCI CAN-S (single SJA1000 channel) board. QEMU startup options::40 -object can-bus,id=canbus041 -device kvaser_pci,canbus=canbus043 Add "can-host-socketcan" object to connect device to host system CAN bus::45 -object can-host-socketcan,id=canhost0,if=can0,canbus=canbus047 (2) CAN bus PCM-3680I PCI (dual SJA1000 channel) emulation::49 -object can-bus,id=canbus050 -device pcm3680_pci,canbus0=canbus0,canbus1=canbus0[all …]
... s %s <no uclass> Driver uid uclass Devices %-25.25s %-3.3d %- ...
2 * QEMU<->ACPI BIOS PCI hotplug interface6 * Interface specification - see docs/specs/acpi_pci_hotplug.txt16 * but WITHOUT ANY WARRANTY; without even the implied warranty of23 * Contributions after 2012-01-13 are licensed under the terms of the30 #include "hw/pci-host/i440fx.h"35 #include "hw/pci-bridge/xio3130_downstream.h"36 #include "hw/i386/acpi-build.h"41 #include "qom/qom-qobject.h"67 return -1; in acpi_pcihp_get_bsel()83 DeviceState *br = bus->qbus.parent; in acpi_set_bsel()[all …]
14 # but WITHOUT ANY WARRANTY; without even the implied warranty of20 # 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.23 Run QEMU with all combinations of -machine and -device types,44 print(" Try 'make check-venv' from your build directory,")49 logger = logging.getLogger('device-crash-test')54 # * Avoiding verbose log messages when we find known non-fatal57 # * Skipping machines/devices that are known not to work out of58 # the box, when running in --quick mode77 {'machine':'niagara', 'expected':True}, # Unable to load a firmware for -M niagara78 … {'machine':'boston', 'expected':True}, # Please provide either a -kernel or -bios argument[all …]
10 --------------------------------------12 ``-hdachs`` (removed in 2.12)15 The geometry defined by ``-hdachs c,h,s,t`` should now be specified via16 ``-device ide-hd,drive=dr,cyls=c,heads=h,secs=s,bios-chs-trans=t``17 (together with ``-drive if=none,id=dr,...``).19 ``-net channel`` (removed in 2.12)22 This option has been replaced by ``-net user,guestfwd=...``.24 ``-net dump`` (removed in 2.12)27 ``-net dump[,vlan=n][,file=filename][,len=maxlen]`` has been replaced by28 ``-object filter-dump,id=id,netdev=dev[,file=filename][,maxlen=maxlen]``.[all …]