| /openbmc/openbmc-test-automation/docs/ |
| H A D | redfish_request_via_mTLS.md | 8 - **MTLS_ENABLED** indicates whether mTLS is enabled in BMC. False by default:
14 - **VALID_CERT** indicates valid mTLS certificate for authentication. When a
21 - **CERT_DIR_PATH** indicates path of mTLS certificates directory:
29 - When a redfish request is executed, it will be executed through the python
41 headers={"Cache-Control": "no-cache"})
44 - Original robot code of redfish request doesn’t need to modify. It will send
47 - The example provides Redfish request to use other certificate in the Robot
56 ## Test Cases for mTLS authentication
59 purposes. Therefore, some test cases need to write a new one to match it for
61 username) Some cases don’t need to be tested because the purpose of them are
[all …]
|
| /openbmc/phosphor-power/phosphor-regulators/test/ |
| H A D | mock_services.hpp | 5 * you may not use this file except in compliance with the License.
8 * http://www.apache.org/licenses/LICENSE-2.0
43 // Specify which compiler-generated methods we want
91 * This allows test cases to use the object in EXPECT_CALL() statements.
103 * This allows test cases to use the object in EXPECT_CALL() statements.
116 * This allows test cases to use the object in EXPECT_CALL() statements.
128 * This allows test cases to use the object in EXPECT_CALL() statements.
140 * This allows test cases to use the object in EXPECT_CALL() statements.
151 * D-Bus bus object.
|
| /openbmc/linux/tools/testing/selftests/tc-testing/ |
| H A D | README | 1 tdc - Linux Traffic Control (tc) unit testing suite
3 Author: Lucas Bates - lucasb@mojatatu.com
10 ------------
24 * All tc-related features being tested must be built in or available as
26 ./tdc.py -c
30 teardown commands - which includes not being able to run a test simply
32 handled in a future version - the current workaround is to run the tests
37 --------------
44 using the -p option when running tdc:
45 ./tdc.py -p /path/to/tc
[all …]
|
| /openbmc/linux/Documentation/dev-tools/kunit/ |
| H A D | usage.rst | 1 .. SPDX-License-Identifier: GPL-2.0
6 Test Cases
7 ----------
13 .. code-block:: c
38 .. code-block:: c
59 To learn about more KUnit expectations, see Documentation/dev-tools/kunit/api/test.rst.
66 additional tests cases which would test each property that an ``add`` function
69 .. code-block:: c
79 KUNIT_EXPECT_EQ(test, 0, add(-1, 1));
85 KUNIT_EXPECT_EQ(test, -1, add(INT_MAX, INT_MIN));
[all …]
|
| /openbmc/openbmc/poky/meta/lib/oeqa/core/ |
| H A D | loader.py | 4 # SPDX-License-Identifier: MIT
49 m = re.match(r'^([0-9a-z_.]+)(?:\.(\w[^.]*)(?:\.([^.]+))?)?$', module, flags=re.ASCII)
65 …nd("All selected modules were skipped, this would trigger selftest with all tests and -r ignored.")
108 self.tc._registry['cases'][case_id] = case
131 # XXX; If the module has more than one namespace only use
140 # 'auto' is a reserved key word to run test cases automatically
190 # monkey patch the default setUp/tearDown{Class} to use
202 # monkey patch the default setUp/tearDown to use
222 Returns a suite of all tests cases contained in testCaseClass.
225 raise TypeError("Test cases should not be derived from TestSuite." \
[all …]
|
| H A D | README | 18 filtering test cases.
25 decorators for Test cases.
27 * oeqa/core/context: Provides OETestContext, a high-level API for
29 OETestContextExecutor a base class to enable oe-test to discover/use
32 Also, a new 'oe-test' runner is located under 'scripts', allowing scans for components
39 * Test data: Data associated with the Test component. Currently we use bitbake datastore as
45 == oe-test ==
47 The new tool, oe-test, has the ability to scan the code base for test components and provide
48 a unified way to run test cases. Internally it scans folders inside oeqa module in order to find
55 $ source oe-init-build-env
[all …]
|
| /openbmc/linux/Documentation/process/ |
| H A D | deprecated.rst | 1 .. SPDX-License-Identifier: GPL-2.0
21 ------------
33 ------------------
34 Use WARN() and WARN_ON() instead, and handle the "impossible"
35 error condition as gracefully as possible. While the BUG()-family
42 <https://lore.kernel.org/lkml/CA+55aFy6jNLsywVYdGp83AMrXBo_P-pkjkphPGrO=82SPKCpLQ@mail.gmail.com/>`_
44 <https://lore.kernel.org/lkml/CAHk-=whDHsbK3HTOpTF=ue_o04onRwTEaK_ZoJp_fjbqq4+=Jw@mail.gmail.com/>`…
46 Note that the WARN()-family should only be used for "expected to
48 but undesirable" situations, please use the pr_warn()-family of
54 open-coded arithmetic in allocator arguments
[all …]
|
| /openbmc/qemu/scripts/simplebench/ |
| H A D | img_bench_templater.py | 3 # Process img-bench test templates
43 return {'error': f'failed to parse qemu-img output: {p.stdout}'}
45 return {'error': f'qemu-img failed: {p.returncode}: {p.stdout}'}
51 Usage: img_bench_templater.py < path/to/test-template.sh
55 stdin. It must be written in bash and end with a `qemu-img bench` invocation
58 Use the following syntax in the template to create the various different test
61 column templating: {var1|var2|...} - test will use different values in
62 different columns. You may use several {} constructions in the test, in this
63 case product of all choice-sets will be used.
65 row templating: [var1|var2|...] - similar thing to define rows (test-cases)
[all …]
|
| /openbmc/openbmc-test-automation/test_lists/ |
| H A D | skip_test_witherspoon | 1 # https://github.com/openbmc/openbmc-test-automation/issues/822
2 --exclude Verify_Minimal_Memory_Buffer_Inventory
3 --exclude Verify_Minimal_Main_Planar_Inventory
4 --exclude Verify_Minimal_System_Inventory
6 --exclude io_board_Present
7 --exclude io_board_Fault
8 # System LED test cases which are NA for Witherspoon system.
9 --exclude Test_Heartbeat_LED_And_Verify_Via_REST
10 --exclude Test_Beep_LED_And_Verify_Via_REST
11 --exclude Test_Identify_LED_And_Verify_Via_REST
[all …]
|
| /openbmc/linux/Documentation/powerpc/ |
| H A D | ultravisor.rst | 1 .. SPDX-License-Identifier: GPL-2.0
16 (PVR=0x004e1203) or greater will be PEF-capable. A new ISA release
25 +------------------+
29 +------------------+
31 +------------------+
33 +------------------+
35 +------------------+
62 to return to a SVM it must use an ultracall. It can determine if
75 +---+---+---+---------------+
79 +---+---+---+---------------+
[all …]
|
| /openbmc/qemu/docs/system/ |
| H A D | security.rst | 5 --------
11 ---------------------
13 QEMU supports many different use cases, some of which have stricter security
18 Virtualization Use Case
21 The virtualization use case covers cloud and virtual private server (VPS)
23 use cases rely on hardware virtualization extensions to execute guest code
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)
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/iommu/ |
| H A D | iommu.txt | 13 Example: 32-bit DMA to 64-bit physical addresses
15 * Implement scatter-gather at page level granularity so that the device does
29 IOMMUs can be single-master or multiple-master. Single-master IOMMU devices
30 typically have a fixed association to the master device, whereas multiple-
34 "dma-ranges" property that describes how the physical address space of the
35 IOMMU maps to memory. An empty "dma-ranges" property means that there is a
39 --------------------
40 - #iommu-cells: The number of cells in an IOMMU specifier needed to encode an
44 the specific IOMMU. Below are a few examples of typical use-cases:
46 - #iommu-cells = <0>: Single master IOMMU devices are not configurable and
[all …]
|
| /openbmc/linux/tools/usb/ |
| H A D | hcd-tests.sh | 2 # SPDX-License-Identifier: GPL-2.0
6 # - control: any device can do this
7 # - out, in: out needs 'bulk sink' firmware, in needs 'bulk src'
8 # - iso-out, iso-in: out needs 'iso sink' firmware, in needs 'iso src'
9 # - halt: needs bulk sink+src, tests halt set/clear from host
10 # - unlink: needs bulk sink and/or src, test HCD unlink processing
11 # - loop: needs firmware that will buffer N transfers
25 # - include unlink tests
26 # - add some ${RANDOM}ness
27 # - connect several devices concurrently (same HC)
[all …]
|
| /openbmc/linux/Documentation/bpf/ |
| H A D | ringbuf.rst | 12 ----------
18 - more efficient memory utilization by sharing ring buffer across CPUs;
19 - preserving ordering of events that happen sequentially in time, even across
23 Both are a result of a choice to have per-CPU perf ring buffer. Both can be
25 problem could technically be solved for perf buffer with some in-kernel
30 ------------------
39 with existing perf buffer use in BPF, but would fail if application needed more
42 Additionally, given the performance of BPF ringbuf, many use cases would just
56 The approach chosen has an advantage of re-using existing BPF map
62 combined with ``ARRAY_OF_MAPS`` and ``HASH_OF_MAPS`` map-in-maps to implement
[all …]
|
| /openbmc/linux/drivers/base/firmware_loader/builtin/ |
| H A D | main.c | 1 // SPDX-License-Identifier: GPL-2.0
24 if (size < fw->size) in fw_copy_to_prealloc_buf()
26 memcpy(buf, fw->data, fw->size); in fw_copy_to_prealloc_buf()
31 * firmware_request_builtin() - load builtin firmware
35 * Some use cases in the kernel have a requirement so that no memory allocator
37 * the x86 CPU microcode loader. In these cases all the caller wants is to see
38 * if the firmware was built-in and if so use it right away. This can be used
39 * for such cases.
41 * This looks for the firmware in the built-in kernel. Only if the kernel was
42 * built-in with the firmware you are looking for will this return successfully.
[all …]
|
| /openbmc/u-boot/drivers/block/ |
| H A D | Kconfig | 7 flash sticks. These provide a block-level interface which permits
8 reading, writing and (in some cases) erasing blocks. Block
10 be partitioned into several areas, called 'partitions' in U-Boot.
24 flash sticks. These provide a block-level interface which permits
25 reading, writing and (in some cases) erasing blocks. Block
27 be partitioned into several areas, called 'partitions' in U-Boot.
36 flash sticks. These provide a block-level interface which permits
37 reading, writing and (in some cases) erasing blocks. Block
39 be partitioned into several areas, called 'partitions' in U-Boot.
43 bool "Use block device cache"
[all …]
|
| /openbmc/bmcweb/ |
| H A D | DEVELOPING.md | 11 - Binaries and static files should take up < 1MB of filesystem size
12 - Memory usage should remain below 10MB at all times
13 - Application startup time should be less than 1 second on target hardware
21 should be avoided if possible, and instead use async tasks within boost::asio.
29 - All buffer boundaries must be checked before indexing or using values
30 - All pointers and iterators must be checked for null before dereferencing
31 - All input from outside the application is considered untrusted, and should be
34 - All error statuses are checked and accounted for in control flow.
35 - Where applicable, noexcept methods should be preferred to methods that use
37 - Explicitly bounded types should be preferred over implicitly bounded types
[all …]
|
| /openbmc/linux/tools/testing/selftests/tc-testing/creating-plugins/ |
| H A D | AddingPlugins.txt | 1 tdc - Adding plugins for tdc
3 Author: Brenda J. Butler - bjb@mojatatu.com
6 --------------
9 There are some examples in plugin-lib.
14 - adding commands to be run before and/or after the test suite
15 - adding commands to be run before and/or after the test cases
16 - adding commands to be run before and/or after the execute phase of the test cases
17 - ability to alter the command to be run in any phase:
18 pre (the pre-suite stage)
23 post (the post-suite stage)
[all …]
|
| /openbmc/u-boot/env/ |
| H A D | nvram.c | 1 // SPDX-License-Identifier: GPL-2.0+
3 * (C) Copyright 2000-2010
6 * (C) Copyright 2001 Sysgo Real-Time Solutions, GmbH <www.elinos.com>
11 * 09-18-2001 Andreas Heppel, Sysgo RTS GmbH <aheppel@sysgo.de>
13 * It might not be possible in all cases to use 'memcpy()' to copy
16 * cases it might be possible to access the NVRAM using a different
19 * NVRAM in those cases I invented the functions 'nvram_read()' and
23 * board that wants to use them.
87 * Initialize Environment use
89 * We are still running from ROM, so data use is limited
[all …]
|
| /openbmc/openbmc/poky/documentation/test-manual/ |
| H A D | intro.rst | 1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
22 This manual is a work-in-progress and is being initially loaded with
25 - *yocto-autobuilder2:* This
26 :yocto_git:`README.md </yocto-autobuilder2/tree/README.md>`
28 Autobuilder. The ``yocto-autobuilder2`` repository represents the
33 - *yocto-autobuilder-helper:* This :yocto_git:`README </yocto-autobuilder-helper/tree/README/>`
35 configuration. The ``yocto-autobuilder-helper`` repository contains
56 drive its integration and testing. Buildbot has a plug-in interface
58 ``yocto-autobuilder2`` repository, adding its own console UI plugin. The
59 resulting UI plug-in allows you to visualize builds in a way suited to
[all …]
|
| /openbmc/phosphor-host-ipmid/docs/ |
| H A D | contributing.md | 5 [OpenBMC C++ style guide](https://github.com/openbmc/docs/blob/master/cpp-style-and-conventions)
13 - Too large: "convert foo to new API; also fix CVE 1234 in bar"
14 - Too small: "move abc.h to top of include list" and "move xyz.h to bottom of
16 - Just right: "convert foo to new API" and "convert foo from tab to space"
21 possible, your commit should stand alone on top of master - "Fix whitespace in
36 send it again to Gerrit. This typically involves `git rebase --interactive` or
37 `git commit --amend`, for which there are many guides online. As mentioned in
44 should be clearly written - even moreso than production code, unit tests are
45 meant primarily to be read by humans - and should test both good and bad
47 [testing documentation](https://github.com/openbmc/phosphor-host-ipmid/blob/master/docs/testing.md)
[all …]
|
| /openbmc/linux/Documentation/livepatch/ |
| H A D | reliable-stacktrace.rst | 16 to identify which functions are live is to use a stacktrace.
19 functions with live state, and best-effort approaches which can be helpful for
38 * The return code is non-zero to indicate that the trace is not reliable.
41 In some cases it is legitimate to omit specific functions from the trace,
42 but all other functions must be reported. These cases are described in
45 Secondly, the reliable stacktrace function must be robust to cases where
47 function should attempt to detect such cases and return a non-zero error
49 an unsafe way. Specific cases are described in further detail below.
52 3. Compile-time analysis
55 To ensure that kernel code can be correctly unwound in all cases,
[all …]
|
| /openbmc/linux/drivers/gpio/ |
| H A D | TODO | 1 This is a place for planning the ongoing long-term work in the GPIO
8 to move away from the global GPIO numberspace and toward a descriptor-based
10 ideally have no use or idea of the global GPIO numberspace that has/was
18 establish the numberspace at compile-time, making it hard to add any numbers
26 The runtime-assigned GPIO numberspace (what you get if you assign the GPIO
27 base as -1 in struct gpio_chip) has also became unpredictable due to factors
28 such as probe ordering and the introduction of -EPROBE_DEFER making probe
37 - Convert all GPIO device drivers to only #include <linux/gpio/driver.h>
39 - Convert all consumer drivers to only #include <linux/gpio/consumer.h>
41 - Convert all machine descriptors in "boardfiles" to only
[all …]
|
| /openbmc/linux/tools/memory-model/Documentation/ |
| H A D | simple.txt | 2 memory-ordering lives simple, as is necessary for those whose domain
3 is complex. After all, there are bugs other than memory-ordering bugs,
4 and the time spent gaining memory-ordering knowledge is not available
5 for gaining domain knowledge. Furthermore Linux-kernel memory model
15 of MMIO-based device drivers will often need to use mb(), rmb(), and
22 Single-threaded code
25 In single-threaded code, there is no reordering, at least assuming
38 this lock at a given time, your code will be executed single-threaded.
52 Please use the standard locking primitives provided by the kernel rather
56 surprisingly hard to correctly code production-quality lock acquisition
[all …]
|
| /openbmc/linux/lib/kunit/ |
| H A D | kunit-example-test.c | 1 // SPDX-License-Identifier: GPL-2.0
3 * Example KUnit test to show how to use KUnit.
55 * This is run once before all test cases in the suite.
66 * This is run once after all test cases in the suite.
150 KUNIT_EXPECT_GT_MSG(test, sizeof(int), 0, "Your ints are 0-bit?!"); in example_all_expect_macros_test()
151 KUNIT_ASSERT_GT_MSG(test, sizeof(int), 0, "Your ints are 0-bit?!"); in example_all_expect_macros_test()
168 return i - 1; in subtract_one()
172 * This test shows the use of static stubs.
200 snprintf(desc, KUNIT_PARAM_DESC_SIZE, "example value %d", p->value); in example_param_get_desc()
206 * This test shows the use of params.
[all …]
|