Home
last modified time | relevance | path

Searched +full:functional +full:- +full:system +full:- +full:fedora (Results 1 – 9 of 9) sorted by relevance

/openbmc/qemu/.gitlab-ci.d/
H A Dbuildtest.yml2 - 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 …]
/openbmc/qemu/tests/functional/
H A Dtest_x86_64_hotplug_cpu.py3 # Functional test that hotplugs a CPU and checks it on a Linux guest
11 # later. See the COPYING file in the top-level directory.
19 ('https://archives.fedoraproject.org/pub/archive/fedora/linux/releases'
24 ('https://archives.fedoraproject.org/pub/archive/fedora/linux/releases'
31 self.vm.add_args('-accel', 'kvm')
32 self.vm.add_args('-cpu', 'Haswell')
33 self.vm.add_args('-smp', '1,sockets=1,cores=2,threads=1,maxcpus=2')
34 self.vm.add_args('-m', '1G')
35 self.vm.add_args('-append', 'console=ttyS0 rd.rescue')
44 'cd /sys/devices/system/cpu/cpu0',
[all …]
H A Dtest_s390x_topology.py3 # Functional test that boots a Linux kernel and checks the console
11 # later. See the COPYING file in the top-level directory.
24 See: docs/system/s390x/cpu-topology.rst.
27 - implicitly from the '-smp' argument by completing each topology
30 - explicitly from the '-device' argument on the QEMU command line
31 - explicitly by hotplug of a new CPU using QMP or HMP
32 - it is modified by using QMP 'set-cpu-topology'
47 '/fedora-secondary/releases/35/Server/s390x/os'
53 '/fedora-secondary/releases/35/Server/s390x/os'
59 failure_message='Kernel panic - not syncing',
[all …]
/openbmc/openbmc/poky/documentation/ref-manual/
H A Dsystem-requirements.rst1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
4 System Requirements
18 ":ref:`overview-manual/development-environment:the yocto project development environment`"
23 :doc:`/brief-yoctoprojectqs/index` document. You can find "how-to"
24 information in the :doc:`/dev-manual/index`. You can find Yocto Project overview
25 and conceptual information in the :doc:`/overview-manual/index`.
30 the :ref:`ref-manual/resources:links and related documentation` section.
35 To build an image such as ``core-image-sato`` for the ``qemux86-64`` machine,
36 you need a system with at least &MIN_DISK_SPACE; Gbytes of free disk space.
40 If you have a shortage of disk space, see the ":doc:`/dev-manual/disk-space`"
[all …]
/openbmc/qemu/docs/about/
H A Dbuild-platforms.rst1 .. _Supported-build-platforms:
25 support for those backports, unless the feature is auto-detectable in a
33 :ref:`setup-build-env` page.
36 ----------------------------
40 .. list-table::
41 :header-rows: 1
43 * - CPU Architecture
44 - Accelerators
45 * - Arm
46 - hvf (64 bit only), kvm (64 bit only), tcg, xen
[all …]
H A Ddeprecated.rst8 it will be listed in this section. The feature will remain functional for the
21 for pre-existing VM deployments. They should be scheduled for updating to a
23 should exclusively use a non-deprecated machine type, with use of the most
24 recent version highly recommended. Non-versioned machine types follow the
30 System emulator command line arguments
31 --------------------------------------
33 Short-form boolean options (since 6.0)
43 The replacement for the ``nodelay`` short-form boolean option is ``nodelay=on``
50 command-line less readable, especially when the argument itself consist of a
51 name and a value, e.g. ``-plugin plugin_name,arg="arg_name=arg_value"``.
[all …]
/openbmc/qemu/docs/devel/testing/
H A Dmain.rst7 everything from unit testing and exercising specific sub-systems all
8 the way to full blown functional tests. To get an overview of the
9 tests you can run ``make check-help`` from either the source or build
13 the meson build system so can be run directly from the build tree,
16 [./pyvenv/bin/]meson test --suite qemu:softfloat
38 -------------------------
49 Different sub-types of "make check" tests will be explained below.
55 .. _unit-tests:
68 In QEMU, unit tests can be invoked with ``make check-unit``. They are
76 1. Create a new source file. For example, ``tests/unit/foo-test.c``.
[all …]
/openbmc/
Dopengrok1.0.log1 2025-11-12 03:01:06.886-0600 FINE t1 Executor.registerErrorHandler: Installing default uncaught exception handler
2 2025-11-12 03:01:06.954-0600 INFO t1 Indexer.parseOptions: Indexer options: [-c, /usr/local/bin/ctags, -T, 12, -s, /opengrok/src, -
[all...]
Dopengrok2.0.log1 2025-11-11 03:01:11.966-0600 FINE t1 Executor.registerErrorHandler: Installing default uncaught exception handler
2 2025-11-11 03:01:12.039-0600 INFO t1 Indexer.parseOptions: Indexer options: [-c, /usr/local/bin/ctags, -T, 12, -s, /opengrok/src, -
[all...]